Solution
You can customize the Process Model. From the article Process Model Theory:
"Why Do I Need a Process Model?
Without a process model, each test sequence would need to provide the mechanism for these common tasks. This code would have to be repeated in each new test sequence created. Any changes to the operation of these common tasks would need to be repeated in each test sequence. Using a process model, you have increased modularity and reusability by keeping all of the code that performs common tasks. Any modifications to the common operations need to be changed in only one common location."
Process Models allow you to create a single file which describes how your sequence files are executed and reported. (Process Models are also .seq files, like Sequence files!)
TestStand uses a Process Model by default, which can be customized or a new one can be created. In TestStand, go to Edit >> Sequence File Properties >> Advanced to select the Process Model (.seq) that you need.
