Video Recording & Slides: Psychology of Testing at Wealthfront Engineering

February 14th, 2011 · 9 Comments ·

Here is a presentation I have done few weeks ego at Wealthfront Engineering.

Enjoy the slides and a recording of presentation!

Tags: Uncategorized

9 responses so far ↓

  • Tweets that mention Video Recording & Slides: Psychology of Testing at Wealthfront Engineering -- // Feb 15, 2011 at 1:03 am

    [...] This post was mentioned on Twitter by solydzajs, testingfeeds. testingfeeds said: [Blog] Video Recording & Slides: Psychology of Testing at Wealthfront Engineering: Here is a presentation I have… [...]

  • Shein Alexey // Feb 15, 2011 at 3:22 am

    Please, fix the video, it’s damaged in several places and some pieces are just cut off. But the remaining part is great, thank you, Misko :)

  • najcik // Feb 15, 2011 at 12:40 pm

    Funny the last question is left unanswered in the video

  • Phil L // Mar 19, 2012 at 8:59 pm

    Testing is a skill like anything else. I think most developers as you said, don’t realize this. You referenced Malcolm Gladwell’s # of hours to be an expert as 2000, but I think the number is 10000! So that would be 5 straight years as a tester! I guess to be an expert tester, that is what it would take. Unit testing makes the end to end testing easier as you mentioned, but how many organizations don’t do unit level testing? I think most developers even in today’s agile environment, do their own ‘checking’ but don’t really test, and still depend on a traditional waterfall, just that the cycles have been shortened.

  • Personal taste for test and quality toolbox « Don't Make the Same Mistake Twice // Jun 16, 2012 at 1:24 am

    [...] unit test as running specifications [...]

  • Bobo // Jun 17, 2012 at 5:00 pm

    Hey Misko, when are you going to drop some of your ‘writing testable Jaascript’ wisdom on us? I’ve been waiting for ages!

  • Dori // Nov 16, 2012 at 4:36 am

    Hi Misko,
    First I wanted to tell you that I’ve been following you for a long time, it has been educating reading and listening to your stuff.
    I have a problem regarding DI while I was struggling with the following problem. Sometimes there are classes which have many dependencies. Imagine an event dispatcher which has many subscribers. One solution (which I don’t like) is to inject the service container to the dispatcher (a.k.a service locator) and that way the dispatcher can access all subscribers. The problem with this solution is that the dispatcher suddenly can access all services. In ideal world I would inject a “subscribers container” which holds only the subscribers. What would you do in such situation?


  • Radha // Jan 30, 2013 at 5:50 pm

    Box Tech Talk Psychology of Testing my feedback and Questions:

    Hi Misko,

    First of all thank you for your wonderful presentation.I was in the event which happened on Wednesday, January 16, 2013 from 6:00 PM to 7:45 PM (PST) I am from a Software Quality Analyst Background.

    When you where discussing about the developers should do unit testing first then functional testing and then Scenario testing with a Triangle Diagram.But from the Quality Analyst Point of View when the developers does their unit testing and when it comes to the tester the tester will be ready with the functional test cases and Scenario test cases and still the testers will be able to find more bugs with their scenario and functional testing and with the domain and Product expertise.

    My question is the testers thinks in more different angle and does positive and negative testing and find more bugs.When the Developers does unit testing they cannot find out like a tester does.So my suggestion for the developers is when they are doing Unit testing they need to add lot of error handling methods in their code when exceptions happens how does the system needs to behave that is the part that the developers should keep in Mind.Do you agree with my point?That too in the Agile development with the testers help the developers will be able to find issues quicker but in the Water Fall method the testers will involve only after certain functionality or module is build at that time even though the developers does their unit testing it will be a cycle the testers find lot of issues at the end and it is hard for the developers to triage the issues what is your advise on it.How can a tester help the development team or the developer at that time?

    I was not able to ask about these questions on the day of the meet up.Could you please give your explanation and your view?I still have more questions and feedback let me wait for your reply and pile my questions later.

    Thank you,


  • misko // Jan 30, 2013 at 10:46 pm

    Yes I agree. The point is that when devs do unit testing, they will enable testability of the product. This will make the job of writing an end to end testing framework easier.