Data model enhancements in Test Management 2.0

  • リリースバージョン: Australia
  • 更新日 2026年03月12日
  • 所要時間：2分

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

    Enhanced traceability

    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.Illustration showing multiple versions of a test Illustration highlighting the version and state on the test form Illustration highlighting the association of a test result with a specific version of a test

    More flexible approach to organize tests

    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.

    Illustration showing that test set is a collection of tests

    Test plan defines the time frame

    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.Illustration showing that a test plan is broken down into test cycles and test execution suites