Test Plan Runs Freezing and Synchronization | Targetprocess - Visual management software

Test Plan Runs Freezing and Synchronization

Available from the version 3.6.0

Test entities in Targetprocess can be organized in the following structure:

Test Plan Runs Freezing and Synchronization. Image 1

When it’s time to execute a test plan, we create a test plan run. The following test run entities are created automatically in it:

Test Plan Runs Freezing and Synchronization. Image 2

Tests and their test runs become strictly tied one to another and when a test is updated, then a related test run needs to be either:

  • Synchronized with a test, i.e. updates made in a test should be applied to a test run

    It’s required when a test run needs to be modified. As a test run inherits information from the related test, to update it we need to make the required changes in a test and the test run will be modified accordingly.

  • Not synchronized with a test entity, or stay frozen, i.e. updates made in a test should not be applied to a test run

    This case is valid when a test execution is completed and the results should be stored ‘as they were at the moment of execution’ forever, i.e. we don’t want any changes to be made in the executed tests even if the related test has been modified.

In the table below you can see what details for every type of a test run will be frozen or synchronized with a related test, when it has been modified.

Entity TypeDetails to freeze or to synchronize
test plan run
  • included test case runs and test plan runs order and presence
test case run
  • test step runs order and presence
  • test case run description
  • test case run name
test step run
  • test step run description
  • test step run expected result

Note: Test order and presence means that when a test is added / deleted / reordered (changed its position in a list), then an appropriate test run will be added / deleted / reordered in a test run.

Freezing Rules

There are simple rules, which describe when a test run should be synchronized with its related test and when it should be frozen.

Rule 1

A test plan run is frozen when at least one of the following conditions becomes true:

  • it is in the final state
  • its parent test plan run is in the final state

Rule 1

In all the other cases the changes made in a test plan will be made in all the related open test plan runs.

If a test plan run has been closed but needs to be updated, just reopen it and all the changes made in a related test plan will be applied to a test plan run.

Test Plan Runs Freezing and Synchronization. Image 4

Rule 2

A test case run is frozen when at least one of the following conditions becomes true:

  • a test case run result - passed/failed/on hold/blocked - is selected
  • its parent test plan run is in the final state

Rule 2

In all the other cases the changes made in a test case will be made in all the related not executed test case runs.

If a test case run has been executed and needs to be updated, you can deselect a test case run result (hover mouse over the run result button and click clear), and all the changes made in a related test case will be applied to a test case run.

Test Plan Runs Freezing and Synchronization. Image 6

Rule 3

A test step run is frozen when at least one of the following conditions becomes true:

  • a test step run result (or status) - passed or failed - is selected
  • its test case run result - passed/failed/on hold/blocked - is selected
  • its parent test plan run is in the final state

Rule 3

In all the other cases the changes made in a test step will be made in all the related not executed test step runs.

If a test step run has been executed and needs to be updated, you can deselect a test step run result, and all the changes made in a related test step will be applied to a test step run.

Test Plan Runs Freezing and Synchronization. Image 8

Note: Please notice that a test step run will be deleted from a test case run, even if it has been executed, if it is deleted from a related test case. At the same time an executed test case run and closed test plan run will not be deleted from a test plan run even if their related test case or test plan were deleted.

Example

Let’s consider an example. Imagine we have the following structure:

Example

A Test Step Run will be frozen if it is executed, or if a Test Case Run is executed, or if a Test Plan Run is in the final state. However a Test Step Run will be deleted even if it is executed and a Test Case Run is not executed or a Test Plan Run is not in the final state.

A Test Case Run will be frozen if it is executed, or if a Test Plan Run is in the final state. It will not be deleted as soon as executed even if a related Test Case is deleted from a Test Plan.

A Test Plan Run 1 will be frozen if it is in the final state, or if a Test Plan Run is in the final state. It will not be deleted as soon as moved to the final state even if a related Test Plan is deleted.

A Test Plan Run will be frozen if it is in the final state.

Conclusion

  1. To freeze Test Plan Run results -> Move a Test Plan Run to its final state.
  2. To freeze Test Case Run results -> Execute it, i.e. select a run result (or status).

Still have a question?

We're here to help! Just contact our friendly support team

Find out more about our APIs, Plugins, Mashups and custom extensions. Join our community of passionate users and even discuss directly with our developers.