Values in output fields are kept between testruns

Technical
1

Hallo,

In our current testplan / teststeps we face the following issues:

  1. Values from the previous test run are still stored in the output fields at the start of a test run. This can lead to unexpected behaviour when a test plan is partially executed on a second run.
  2. Verdicts from the previous test run are not automatically cleared at the start of a new test run. This again can lead to unexpected behaviour.
  3. Due to the different output fields the plan hash is always different. We would prefer if the hash is consistant over several runs, if that is possible.

For point 1 and 2 we currently set the output fields and verdict to a default state in the PrePlanRun of a test step. This does not solve point 3.
So we are wondering if Opentap provides a solution for these issue, or if we should take a different approach.

I have bundled the three issues in one topic since I think they all have the same root cause.

2

We have gained some new insights:

As for point 1: We suspect that the output values are updated by the keysight editor. And not directly through the OpenTap API. But we are not sure.

When a testplan is referenced, through the basic test step, the referenced steps are not updated.