Blog‎ > ‎

5 Ways to Revolutionize Your QA - Summary

posted May 7, 2012, 7:45 PM by Unknown user   [ updated May 7, 2012, 7:46 PM ]
5 Ways to Revolutionize Your QA




James Whittaker explains five insights to change the way the testing process is done. The problem is when the testing team loses the big picture of the problem and focuses only on day-to-day details.


Insight 1: Two types of code


User experience code and infrastructure code is not the same. James tells a story when automation tests stop finding bugs eventually. He describes why this happened. Automation tests aren’t good for everything. Automation is good for infrastructure code e.g. connections to databases, connection to servers, network, etc. and for user experience code (domain logic, business logic) manual testing is the way to go. Have you heard about the pesticide paradox? It’s when testing kills some bugs, but other bugs become resistant to the pesticide. The chemical formula of the pesticide has to be changed to kill those resistant bugs. You need to identify what type of code you’re working with to execute the right tests.


Insight 2: Test capabilities not features


Features are not simple enough to test. Decomposing features into capabilities makes testing simpler and easier. This way, all features are being tested step by step.


Insight 3: It’s about technique


Test cases are used to find bugs. The test case is not the important thing when finding a bug, but the logic behind it. James proposes using “tours” to guide testers. A tour is for a specific area of the software to test. This tour includes guidance to the tester, help the tester think through inputs or data or any other information. It’s like a real tour where you have maps, taxis, guidebooks, etc. The goal is to help testers to be more productive and improve their results.


Insight 4: Testing is not about bugs


Finding bugs is not the main goal of testing. Testing is also to ensure that the customer requirements are being covered, ensuring quality, etc. Finding bugs is just a part of testing. The goal is to ensure quality by fixing those bugs. James gives some advices to help developers build better software.


Insight 5: Testing should not suck


Don’t make testing boring. Testing shouldn’t be tedious and repetitive. There are many ways to make testing fun. You can create games and give prizes, or maybe create your own tours. Innovate to transform the testing process. When someone enjoys what he does, the results are better.


Javier Rojas D.

Comments