Test Management 2.0 overview
Test Management 2.0 helps you deliver software products more efficiently and with fewer defects by managing and streamlining testing processes for both testers and managers. You can create multiple versions of a test and integrate with Agile Development 2.0.
To learn about the different versions of Test Management and to choose the version that helps you meet your testing requirements, see Test Management applications.
| User | Description |
|---|---|
| Tester | Can run tests and report defects on a software product by:
|
| Test Manager | Can set up and monitor the manual testing process of a software product by:
|
Key terminology
The following section describes the key terms used in Test Management 2.0.| Term | Description |
|---|---|
| Test | A collection of conditions or steps used to determine whether a feature is working
correctly. A test can also include an expected result, which is used to determine if the
test case passes or fails. You can use the Tests module to create and maintain different versions of a test. |
| Test set | A collection of related tests. A test can be a part of one or more test sets. You can use the Test Sets module to create a test set and group related tests into that test set. |
| Test plan | Plan describing how a product or a feature is to be tested and the time frame in which
it must be executed. A test plan can be further broken into test cycles, and test cycles
into test execution suites. You can use the Test Plans module to create test plans. |
| Test case | A collection of related tests. A test case is saved as part of a test suite and can be added to a test plan. Each test case within a test plan has an assigned tester. |
| Runs | Detailed report of tests results, such as start time and end time of test execution,
environment details, result of test execution. You can use the Run module to view the test results. |