January 9, 2013

Three Easy Steps for Managing Regression Test Cases

Helix ALM
If you have ever been tasked with creating a regression test case suite from a large number of test cases, you know how tedious and time-consuming it can be. To save the time it takes to go through thousands of test cases, you can use TestTrack’s folders and filters to ease the burden. For those of you who already use folders to organize or group test cases used for regression testing, the process is very easy to implement. If you do not already use folders, you’ll need to begin creating folders that contain regression test cases for each release (when creating a regression test run suite, choose test cases from your “Full Regression” suite). Once the folders have been created, follow these three easy steps: 1. Create a Filter: Exclude folders that contain regression test case suites from the last few releases.  For example:   The number of folders to exclude will differ based on various factors specific to your organization, such as how often you release your product, how your folders are organized, etc. 2. Tweak the Filter: Exclude other test case restrictions that are not relevant to the regression test suite you are creating for the release. For example:   The number of items to include or exclude will differ based on various factors, such as test runs that failed during the prior release, high/low risk functional areas, etc. 3. Apply the Filter from the Test Cases window: Sort test case columns by criteria that makes sense for your project (Functional area,  Summary, etc.) Now you can quickly and easily select test cases from the filtered list. This ensures that you are getting good test coverage and not executing the same tests release after release.

Solutions for Special Conditions

  • Smoke tests: Create a special folder, (e.g., "Always Run") for tests that need to be run each release
  • Test cases not in folders: Create a filter that excludes test run sets from prior releases
  • Large number of test cases: Exclude a greater number of ‘already run in prior release’ folders, and choose a sub-set of test cases from them