In this episode of Coding QA, Mark and Jim discuss applying the lessons learned from past experiences to produce a better product. First, they discuss improving the quality of the Coding QA podcast itself by leveraging their experiences with professionally produced podcasts. Then, they discuss Microsoft examples of learning from historical failures, using post mortems to prevent future failures and the value of learning from others.

 

Links from the show:

• This Developer's Life

In this episode of Coding QA, Mark and Jim continue applying the "Test Techniques" defined in James Bach's Heuristic Test Strategy Model. They walk through the categories of Claims, User, Risk and Automatic testing and apply them to a typical household toaster. At the same time, they relate their thought processes and test scenarios back to real world software testing.

 

 

Links from the show:

• Toaster Instructions used during Claims testing evaluation

• James Bach's Heuristic Test Strategy Model

In this episode of Coding QA, Mark and Jim embrace your poll feedback (focus on testing tools and techniques) and take a look at the "Test Techniques" defined in James Bach's Heuristic Test Strategy Model. They walk through the categories of Function, Domain, Stress, Flow and Scenario testing and apply them to a typical household toaster. At the same time, they relate their thought processes and test scenarios back to real world software testing.

 

To help you follow along, here's the toaster they're testing:

 

 

 

Links from the show:

 

• James Bach's Heuristic Test Strategy Model

• James Bach's blog

 

It's been over half a year since Jim and Mark took over the Coding QA podcast and while they're having a lot of fun putting the shows together, they would like to make sure that you, dear listener, are getting to hear what you want to hear.

To help guide their future show topic selection, they've put together this tiny (one question) poll.  Please take 15 seconds out of your day to provide them with this value feedback.

 

The poll is now complete. Thanks for all of your feedback.

 

Also, if you have any general feedback about the show (format, recording quality, etc.) please don't hesitate to send mail to Mark or Jim.

 

In this week's episode of Coding QA, it's just Mark (Jim's on vacation) discussing the topic of Setup Testing. Recently asked to review a setup test plan, Mark takes a step back to draft a mini-framework for defining a comprehensive setup test plan as well as providing guidance for the execution of the test plan and verification of the results. 

 

Listen in as he discusses:
 

• Different categories of variables to help define individual setup test scenarios

• Streamlining and prioritizing a matrix of setup test scenarios

• The use of external resources to assist with running setup test scenarios

• Verification tips to ensure setup has succeeded

 

 

Links from the show:
 

• Mark's blog posts on "Setup Testing - Planning" and "Setup Testing - Execution and Verification"

• Pairwise testing tools including PICT from Microsoft.