Test Management 2.0 overview
Summarize
Summary of Test Management 2.0 Overview
Test Management 2.0 is designed to enhance the efficiency and quality of software product delivery by streamlining testing processes for both testers and managers. It allows for the creation of multiple test versions and integrates seamlessly with Agile Development 2.0, helping teams choose the most suitable testing approach.
Show less
Key Features
- Tester Capabilities: Testers can create tests, perform them, update statuses, and report defects, as well as retest as necessary.
- Test Manager Capabilities: Managers can set up and oversee manual testing, create test plans, break them into cycles, assign tests, and monitor progress and results.
Key Terminology
- Test: A set of conditions or steps to verify a feature's functionality, including expected outcomes.
- Test Set: A group of related tests, which can be created and maintained in the Test Sets module.
- Test Plan: A detailed outline of the testing process and timeline, which can be divided into test cycles and execution suites.
- Test Case: A collection of related tests within a test suite that can be included in a test plan, each with an assigned tester.
- Runs: A report detailing the results of tests, including execution times and environment specifics, accessible via the Run module.
Key Outcomes
By utilizing Test Management 2.0, teams can expect improved efficiency in the testing process, reduced defects in software products, and better overall management of test activities. This structured approach facilitates effective communication and collaboration among testers and managers, ultimately leading to higher quality software delivery.
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. |