Migration from Test Management 1.0 to Test Management 2.0
Summarize
Summary of Migration from Test Management 1.0 to Test Management 2.0
This guide helps ServiceNow customers migrate their test data from Test Management 1.0 to the enhanced Test Management 2.0. The migration enables customers to leverage improved testing capabilities and features offered in version 2.0. It is recommended to first perform the migration on a non-production instance to verify accuracy before applying it to a production environment.
Show less
Migration Steps
- Activate Required Plugins: Enable the
Test Management 2.0 (com.snc.testmanagement.2.0)andTest Management 2.0 — Data Migration (com.snc.testmigrationv1v2)plugins to prepare your instance for migration. - Convert Test Suites: Migrate existing test suites along with their test cases into the new structure, converting test suites into test sets and test cases into test versions.
- Verify Migration: Check that data has migrated as intended on a non-production instance before executing the migration on production.
Data Migration Details
- The migration transfers test suites, test cases, and tests but does not migrate test plans due to significant data model changes.
- Data from Test Management 1.0 remains intact and is not removed after migration.
- Mapping of Objects:
- Test Case (1.0) becomes Test Version (2.0), preserving short description, domain, and relationships such as prerequisites and test set links.
- Test (1.0)Test Step (2.0), maintaining order, domain, detailed description, test data, expected results, and verification steps with links to the original test.
- Test Suite (1.0)Test Set (2.0), preserving name, owner, and domain information.
Custom Fields Migration
If you have added custom fields in Test Management 1.0 tables, you can migrate these to corresponding custom columns in Test Management 2.0 by overriding the default field mappings. This is done by modifying the TestMigrationTableMapping script include, which extends the base mapping defined in TestMigrationTableMappingBase. This ensures custom data is preserved during migration.
Migrate your test data from Test Management 1.0 to Test Management 2.0, and start using Test Management 2.0 for its enhanced testing capabilities and features.
Apply the following migration steps on a non-production instance, verify if the migration is completed as intended, and then perform the migration steps on a production instance.
Migration steps
To migrate your test data from Test Management 1.0 to Test Management 2.0, complete the following steps in order:
- Activate the required plugins. For more information, see Migration from Test Management 1.0 to Test Management 2.0.
- Convert your test suites. For more information, see Convert test suites.
- Verify the migrated data on a non-production instance before repeating on production.
Activate plugins
Activate the Test Management 2.0 (com.snc.test_management.2.0) and Test Management 2.0 — Data Migration (com.snc.test_migration_v1_v2) plugins.
Migrate data
- Test plans cannot be migrated due to significant change of data model.
- Test suites, test cases, and tests that are migrated to Test Management 2.0 will not be removed from Test Management 1.0.
| Test Management 1.0: Test case | Test Management 2.0: Test version |
|---|---|
| Short Description | Short Description |
| Domain | Domain |
| Test Suite | Creates a relationship between test and test set |
| Prerequisites | Link to the old test case |
| Test Management 1.0: Test | Test Management 2.0: Test step |
|---|---|
| Order | Order |
| Domain | Domain |
| Detailed description | Link to the old test |
| Test | Step |
| Test data | Link to the old test |
| Expected result | Verification step |
| Test set in Test Management 1.0 | Test set in Test Management 2.0 |
|---|---|
| Name | Name |
| Owner | Owner |
| Domain | Domain |
Add custom fields to migration
You have added custom fields to the tables of Test Management 1.0, and want to move the fields to the corresponding custom columns in Test Management 2.0. In such a case, include the custom fields into migration by overriding the mapping information in the script include TestMigrationTableMapping. The default mapping is provided in the script include TestMigrationTableMappingBase.
Convert test suites
Convert test suites with underlying test cases to test sets and tests.