The Four T's of Test Automation

Historically, organizations have measured the level of software quality after a system goes into production. What about measuring the level of software quality coming into testing? By measuring the number of test cases that pass or fail, and calculating the failure rate, you can forecast future failure rates and the number of test cases that will have to be executed each day during test. Then, you will have the information needed to adjust resources, timelines, and level of effort. Join Jan Fish to learn how to manage and control your testing effort rather than having it control you. By tracking the number and severity of bugs by build, you can open a whole new world of information. Combining this metric with knowledge of the content of the build lets you see immediately if newly introduced functionality is stable, if it disrupts surrounding functionality, or if your test effort should be modified. All this with just five minutes a day effort and a simple spreadsheet--what could be better?

• Spreadsheet to help forecast first run failure rates
• Areas needing process improvement identified easily
• Measures for the effectiveness of process improvement