Test Planner Tutorial

Introduction to Test Sets

A test set is a set of test cases that are associated together for a particular testing task, e.g., all test cases for a particular scenario, all test cases of a particular type, etc. By associating test cases into a test set, you can track the execution of these test cases for that scenario.

Often, an individual test case needs to be executed in association with more than one scenario. Therefore, test cases can be associated with more than one test set. The execution history of a particular test case is specific to the test set, so if a test case is associated with more than one test set, its execution history is separate for each test set.

To access test execution functionality, click on 'Test Execution' in the navigation bar:

Figure: Navigation bar showing 'Test Execution' link

Clicking on 'Test Execution' will display all test sets for this project.

Figure: Test Execution page showing list of test sets

For our sample 'Email Client' project, we've created two test sets version 1.0: one each for functional and volume tests. Separating test cases by type is particularly useful if you have different team members focusing on performing different types of testing (e.g., separate functional and performance test teams).

For release 1.1, notice that there are three test sets:

Release 1.1 functional tests
Release 1.1 volume tests
Release 1.1 functional regression tests

In this example, when testing for release 1.0 was complete, the 'Release 1.0 functional tests' test set was copied to become the functional regression test set for release 1.1. by copying the test set, the execution history for release 1.0 is preserved, and a new test set is created to track the execution of the same tests as regression tests for release 1.1.

If, for instance, some of the release 1.0 test cases are no longer relevant for release 1.1 (due to functionality changes, for instance), these test cases can be removed from the 'Release 1.1 functional regression tests' test set.