December 9, 2011

10 Ways You Know You Need a New Approach to Test Management

Helix ALM
Remember when you used to be able to track test cases and pass/fail results in a simple spreadsheet? It took all of 30 minutes a week to update the data, and no one asked for it more often than that. However, over time, the need for more precise and timely test information grew and the spreadsheet grew too. At the same time, the applications you test also became more complex. You started with 100 test cases but you're currently up to 400 and counting. Your spreadsheet now includes more information about each test case, such as when a test case was run, how long it took, where it failed, if a defect report was created, how long it took the defect to be resolved, and much more. That spreadsheet now has several dozen columns, with a jumble of dates, numbers, and text. You can't easily view or report on the data you're tracking. One day you realize your simple spreadsheet has become an unwieldy mess. You spend more time each day making sure it's up-to-date because management is constantly asking for progress and issue updates, yet you can't reliably identify any testing trends or prove that all features are being tested. You now spend your days managing the spreadsheet and entering the other testers' data, instead of working on your own test case backlog. [caption id="" align="aligncenter" width="270" caption="Confusing & unwieldy test management"][/caption] You're probably looking at the spreadsheet and wondering if it's time to take the next step and find a better system. How do you know if you've outgrown your homegrown way of managing test cases? Our eBook, 10 Ways You Know You Need a New Approach to Test Management, provides ten signs to look out for.