How to Get What you Want from Testing – Hangout with Michael Bolton

You can type your questions for Michael below and we will address these during the Hangout.


BiographyMichaelBolton JPG

Michael Bolton is a software tester, consultant, and trainer with 20 years of experience around the world, testing, developing, managing, and writing about software. He is the co-author (with senior author James Bach) of Rapid Software Testing, a course that presents a methodology and mindset for testing software expertly in uncertain conditions and under extreme time pressure.

Currently, he leads DevelopSense, a Toronto-based consultancy. Prior to that, he was with Quarterdeck Corporation for eight years, during which he managed the company’s flagship products and directed project and testing teams both in-house and around the world.

Contact Michael at [email protected], or through his Web site,

Related Content

About the Author


Hi everybody! I am part of the marketing team here at TESTHuddle and I look after content generation. I am a big rugby fan and love to watch Munster and Ireland matches. I have a beagler (beagle/king charles cavalier cross) pup called Nelson. I look forward to interacting with you guys!
Find out more about @daraghm

45 Responses to “How to Get What you Want from Testing – Hangout with Michael Bolton”

  1. the topic is ‘How to get what you want from Testing’

    I’d assume we need to start with what one can get out of testing. Not sure if testers can give yet an answer on this. (: can you comment on this 🙂

  2. need to work on my questions 🙂 I tried to look at this topic ( as not a tester) but an external person. Establishing the baseline – what a client should expect from testing 🙂

    there are many stereotypes – and misunderstandings on that testing is.
    Partially you already answered just now -> “by talking to them.”

    Letting the client know what are the things they would benefit – so afterwards they can ask for the testing aspects that would fit their needs and meet their business value.

    For us as a testers to tackle that would be to expose our “sales” people tho these ideas so this is taken into account, right 🙂

  3. Jayne

    I cant see any other comments here currently but there are some interesting topics discussed 🙂 I am interested in learning about the Rapid Software testing. Alot of the time we find that when deadlines draw near, testing time is cut. I have seen this over the years with various companies, how can we improve this scenerio without reducing the test coverage?

  4. Michael will be conducting the following presentations at EuroSTAR 2014:

    What’s The Problem? Delivering Solid Problem Reports ––delivering-solid-problem-reports


    Every Tester Has a PRICE: Sources of Product and Project Information ––sources-of-product-and-project-information

  5. Encourage – expose testers to the testing ideas that are out there 🙂

    answer from experience – the more one gets exposed to a company of passionate driven testers – the harder it’s to hit the breaks, and become ignorant 🙂

    so this is kinda a thanks to everyone who’s seeking out other testers for inspiration, support and knowledge – mentor-ship if you wish

    Thank you crazy testing folk (:

  6. Here are some of the books Michael Mentioned. (I’ll post the rest of the books later):

    Thinking fast and slow –

    Tacit and Explicit Knowledge –

    Lessons Learned in Software Testing –

    The Shape of Actions –

    Code –

    Explore it –

  7. Maaret had a nice post regarding tester and automation ->

    the point that got me ->

    With all this, I find the ‘testers should code’ ‘why would a tester not learn to code’ a generally upsetting theme. Why should I want to be a mediocre coder when I can be a brilliant tester? Or why should I give up my aims of excellence in testing to learn coding to a level I consider professional?

Leave a Reply