Debug Test Results Logs

When testing a lot, you can generate a Debug Test Results Log of human-readable text that contains the measurement values and test limits for tests on all test steps that execute on each site.

The Debug Test Results Log result processor generates a separate file for each site in the test program. You can use this data to debug test issues and to diagnose issues on the tester itself.

The Debug Test Results Log contains the following sections for each DUT:

  • Header—Contains the Site Number, Batch Number, and Part ID for each DUT tested. The Batch Number refers to the loop iteration when testing multiple DUTs. The Debug Test Results Log result processing plug-in populates the Part ID field from the TestStand SerialNumber property, which ECU Software Toolkit sets to the values returned in the SitePartIds parameter.
  • Step Results—Contains the Step Name and all its corresponding tests.
  • Test Results—Contains the Test Number, Result, Test Name, Low Limit, Measurement Value, High Limit, and Units.

Modifying the Number of Results to Include

By default, the Debug Test Results Log includes all test results. You can change the default behavior.

Complete the following steps to log results only when a DUT fails.

  1. Launch the Debug Test Results Log Options dialog box.
  2. Enable the Log Results Only for DUT Failures option.

Complete the following steps to limit the number of results to display for the Debug Test Results Log.

  1. Launch the Debug Test Results Log Options dialog box.
  2. Enable the Limit Number of Results Displayed in Report View option.
  3. Use the Display Results for Last option to specify the number of tests to display in the Report View for the Debug Test Results Log.

Changing Report Orientation

By default, the Debug Test Results Log uses portrait orientation. Landscape orientation uses wider columns for tests with long test numbers or test names. Complete the following steps to change the report orientation of the Debug Test Results Log.

  1. Launch the Debug Test Results Log Options dialog box.
  2. Use the drop-down listbox of the Report Orientation option to select Portrait or Landscape.

Customizing the Filename

When you customize the log filename, use unique filenames for each test site. The Debug Test Results Log result processing plug-in appends results from each DUT to the corresponding site log.

Logging Text Data

If you want to add data to the Debug Test Results Log that is not a measurement or test limit, you can include text data in the Debug Test Results Log by using the following techniques:

  • Adding Text Data for a Step Using Additional Results—You can use the Additional Results panel of the Step Settings pane to add text data after all the measurements and test limits for the tests associated with the step. To configure the Additional Results panel to generate text data in the Debug Test Results Log, set the Name option of the result to NI.TestResultsLog and set the Value to Log option to the value you want to add to the log file. You can optionally add a text label for the data by adding it to the end of the Name field in the form NI.TestResultsLog.CustomTextLabel, where CustomTextLabel is the text you want to display as a label in the log file.
  • Adding Text Data between Test Steps—If the text data you want to log is not associated with a specific step, you can use the Additional Results step type to add text data to the Debug Test Results Log. Use the Additional Results panel of the Step Settings pane as described above to add data to the log file.