Test Management 2.0 overview
Summarize
Summary of Test Management 2.0 overview
Test Management 2.0 in ServiceNow Zurich release streamlines and manages software testing processes to help deliver higher quality products with fewer defects. It supports creating multiple test versions and integrates with Agile Development 2.0. This application is not enabled by default and requires activation of thecom.snc.testmanagement.2.0plugin to use.
Show less
Key Features
- Tester capabilities: Create and organize tests and test sets, execute tests, record results, update test statuses, and manually create defect records linked to failed tests for retesting.
- Test Manager capabilities: Oversee the manual testing process by creating and maintaining tests, test sets, and test plans. Test plans can be subdivided into test cycles and execution suites. Managers assign tests to testers, monitor progress, evaluate results, and close test plans.
- Test Plan and Sprint Testing: Use test plans for structured release readiness across multiple cycles and suites. Alternatively, sprint testing links tests directly to Agile stories for sprint-by-sprint tracking.
Key Terminology
- Test: Steps or conditions to verify a feature's functionality, including expected results. Multiple versions can be maintained.
- Test Set: Grouping of related tests.
- Test Plan: Document outlining testing scope and schedule, divided into test cycles and execution suites.
- Test Cycle: A phase or iteration within a test plan, such as regression or sprint cycles.
- Test Case: Related tests saved within a test suite and assigned to testers.
- Runs: Detailed reports of test executions including timing, environment, and results.
Getting Started
- Activate the Test Management 2.0 plugin.
- Create tests and organize them into test sets.
- Create test plans and assign tests to testers.
- Execute assigned tests and record results.
Practical Considerations for ServiceNow Customers
By utilizing Test Management 2.0, customers can efficiently organize and monitor both manual and sprint-based testing efforts within ServiceNow. This enables better defect tracking, clearer test ownership, and enhanced visibility into testing progress and outcomes across development cycles. Activation is required before use, and customers should choose between structured test plans or sprint testing based on their Agile processes.
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.
Test Management 2.0 is not active by default on all instances.
To use Test Management 2.0, activate the
com.snc.test_management.2.0 plugin. For more information,
see Activate Test Management 2.0.
| User | Description |
|---|---|
| Tester | Can run tests and track defects for a software product by:
Important:
To record a defect for a failed test in Test Management 2.0, create a defect record manually and reference the test in the defect description. |
| 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. To test individual stories sprint by sprint instead, create Tests directly from the Sprint Tracking view. For more information, see Sprint testing. |
| Test cycle | A subdivision of a test plan that represents a phase or iteration of testing, such as a regression cycle or a sprint cycle. A test plan can contain multiple test cycles, and each test cycle can be further divided
into test execution suites. Use the Planning tab on the Test Board to create and manage test cycles. |
| 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. |
Getting started with Test Management 2.0
- Activate the Test Management 2.0 plugin. For more information, see Activate Test Management 2.0.
- Create your first test. For more information, see Create a test in Test Management 2.0.
- Create a test set to organize related tests. For more information, see Create a test set in Test Management 2.0.
- Create a test plan and assign tests to testers. For more information, see Create a test plan using Test Board in Test Management 2.0.
- Run your assigned tests. For more information, see Run your test assignments in Test Management 2.0.
Test plans vs. sprint testing
Use a test plan to organize release-readiness testing across test cycles and test execution suites. Use sprint testing to link tests directly to Agile stories and track them sprint by sprint. For more information, see Sprint testing.