Which is the best way to backup the default TestStand reports?

[lc_garza]

I want to have the ability to protect the partial results of my sequence from being lost. This in the case that a failure in my computer occurs before the report gets generated at the end of the execution. Which would be the best way to do this? Do I need to follow the On-the-Fly Report generation philosophy in order to accomplish this?

Otherwise, I would like to know if it is still possible to use the default report generator.

I saw the OnTheFlyReportGeneration example. In its readme document, it mentions a technique which uses the RunState.Report object, and calls its method Save to store the partial results. Are these the results generated from the ProcessModelPostStep callback? Can these results be store
d from a different place (not the callback)?

What kind of step should I insert in the middle of my test sequence in order to perform the backup of the partial results?

Thanks for your help.

[Scott_Richardson]

Since the default report is not created until you complete the MainSequence call for the UUT, and the results are just fragmented trees of result property objects in memory. You will have to follow the On-The-Fly report generation philosophy.

Yes the results used in the example are the ones generated from the ProcessModelPostStep callback.

Note that results from a called sequence are not attached to the calling sequence until the call is complete. Until the call is complete and the call stack depth decrements, there is no full tree of the existing results in memory.

Technically you could process partial completed results
within your sequence if you are careful to pass in the appropriate data that the report generation sequences require.

Scott
Richardson