When you create a CSV file with the New CSV Output Stream step type, you can attach it the current execution if you name the stream. The name must be unique within the scope of the execution. Providing this name (or the optional ExecutionOutputRecordStream object reference) to a Write Record step allows you to display the data being written to the CSV file in the Report view in real time.

You can limit the amount of data displayed in the Report view with the Records to Display option. Specify a positive value to display only the most recently written records. Specify -1 to display all records. Specify 0 to disable updates to the Report view which will improve performance.
Note   Specifying -1 means that the memory used by the Report view grows linearly with the amount of data written.

Although you can view data written to an output CSV file in the Report view, the CSV file is not a TestStand report as it is not otherwise connected to TestStand reporting features. TestStand reports are driven by process models with their data coming from step results. Using Data Streams, sequences can create and store data to CSV files without running in a TestStand process model. If they do run in a process model, they can still generate ATML, XML, ASCII, HTML, or custom reports. Reports generated using the process model do not interfere with the CSV output file, and the CSV output file does not interfere with reports generated by the model. There is no implicit connection between step results and data written to CSV files. Only data specifically written using Data Streams step types or the TestStand API is stored to the CSV file.

For a demonstration of TestStand Data Streams, see the <TestStand Public>\Examples\Fundamentals\Using Data Streams examples.