Customize test report FAILED on TestStand 1.0.3

[TommyCVI]

Hi,

I have a TestStand 1.0.3 and I would like to customize the test result report.

I wish that in the test report, even if FAILED, were inserted into both the results of any step PASS, FAILED and measures that have not been executed.

I wish all test reports generated by the PC always contain the same number of results (if PASS OR FAILED)

Currently the test report terminate at the FAILED measure (and does not show the measures were not execute).

It's possible?

Best Regards

[Norbert_B]

Out of curiosity: What OS are you using?

TS 1.0.3 is now more than 14 (in words: FOURTEEN) years old and unsupported for about a decade now. See TestStand support life cycle here.

That being said, i can think of several reasons for the behavior you are seeing. In order to narrow it down, one question:

Are you sure, that TS continues testing after the failing step? Or is the failing step simply the last step which is executed?

Please note that report only includes EXECUTED steps. Due to "goto's" and other dynamic execution properties, the list of steps in the sequence does not necessarily indicate the actual order of execution during runtime.

Norbert

[TommyCVI]

Hi,

I use Windows XP!

The TS, when the measure is FAILED stop the cycle (this is correct).

TS work fine!

I wish that in the "Test Report" are also added all the measurements not execute.

For example, I have:

Sequence 1 PASSED

Sequence 2 PASSED

Sequence 3 FAILED - > STOP CYCLE

Sequence 4 NOT_EXECUTE (Previous FAILED)

I wish that in the test report there is:

Sequence 1 PASSED

Sequence 2 PASSED

Sequence 3 FAILED

Sequence 4 NOT_EXECUTE

Actually the test report is:

Sequence 1 PASSED

Sequence 2 PASSED

Sequence 3 FAILED

Thanks

[Norbert_B]

I think that TS 1.0.3 works similar to current versions of TS regarding reporting...at least on a general scope.

That being said, TS nowadays collects results during execution. So only executed steps/sequences can generate results which are collected. If the step is not executed at all, it will not create results, none are collected.

This collection of results is later on used to generate the report. So there is some mechanism browsing to all collected results (ResultList) and generating a growing string containing all information the report should contain (so depending on the report settings). If a step didn't create results, the step never shows up in the ResultList, the report generation will never add any information on that step (as it never executed!).

In this case, there are several options to address that. The easiest might be:

- Do not terminate execution in case of a FAIL

- Create a precondition for each step which will skip step execution if the previous step failed. This will result in the step showing up in the ResultList (so potentially the report) with the status "Skipped".

In case this is enough for you, you are done here. Otherwise, you have to continue:

- In the report generation (part of the "process model"), you already browse each step, potentially including filtering for step results. Identidy that code and search for "Skipped" and replace it by "Not Executed".

Norbert