---
sourceDocument: Xanadu Strategic Portfolio Management
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/it-business-management

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Strategic Portfolio Management

ft:clusterId :

    - itbm

bundleId :

    - itbm

workflow :

    - Technology


---

# Data model enhancements in Test Management 2.0

# Data model enhancements in Test Management 2.0 {#ariaid-title1}

* Release version: Xanadu
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Test Management 2.0 offers a few
data model enhancements over Test Management 1.0.

## Enhanced traceability {#data-model-enhancements-test__section_o2b_qny_khb}

Each test in Test Management 2.0 can have multiple versions. When a test version is in the state Ready, it can be run but cannot be edited. Every test result is associated with a specific run and a specific version of the test. Due
to this logic, you can always be sure of the content of the test when a specific test result was received.

## More flexible approach to organize tests {#data-model-enhancements-test__section_q2d_54y_khb}

Unlike Test Management 1.0, where test
cases can be placed in only one test suite, in Test Management 2.0 tests can be placed in
multiple test sets. Test sets are free-form collections of tests. Tests can be grouped into
test sets using any logic: by product, by component, or by release.

## Test plan defines the time frame {#data-model-enhancements-test__section_n2l_3py_khb}

A test plan in Test Management 2.0
captures the time frame during which the tests are to be run. In addition, a test plan can
be broken down into smaller planning windows, test cycles, for more precise planning, such
as user acceptance testing, and integration testing. Further test cycles can be broken down
into test execution suites, which are similar to sprints in testing. A test execution suite
defines when a test must be run and by whom.