To avoid overloading the WATS-dbase we only record test steps in Teststand that contain information useful to our clients.
This however has consequences when you try to analyse the execution time of the sequence because WATS only shows the execution time of the recorded test steps.
- It would be useful if you would have the option to also show the start-timestamp of the step (which Teststand stores anyway).
- The "test execution time"-analysis of WATS also doesn't work when using selective test step recording because sometimes a lot of non-recorded actions precede the test step that is recorded (but those actions actually belong to the test step and take up most of the execution time). An option that uses the inter-test-step-time instead of the test-step-execution-time could make this work better (using the end-time-stamp).
Please sign in to leave a comment.