On-The-Fly Reporting and Logging in TestStandPrimary Software: TestStandPrimary Software Version: 3.0 Primary Software Fixed Version: N/A Secondary Software:
Problem: I do not want to log my report information at the end of the sequence. Is there a way to do on-the-fly reporting and logging in TestStand? Solution: The ability to log test results concurrently with an execution is a feature of TestStand 3.0. By default, all versions of TestStand will wait until an execution is complete before logging all results to a database or writing the UUT report file to disk. Below is a description of on-the-fly reporting and logging for TestStand by version. TestStand 3.0: In TestStand 3.0 there are check boxes on both the Report Options dialog box and Database Options dialog box, in which you can enable/disable on-the-fly reporting and logging. Both of these reporting behaviors leverage callbacks at the process model level, using the ProcessModelPostResultListEntry and SequenceFilePostResultListEntry callbacks to process the step results. The final data logged is essentially identical to the data generated by the process model at the end of execution. When you use on-the-fly reporting, you can select the Report tab in the Execution window to view the test report during the execution. If the Report tab is the active view of the Execution window while a sequence is executing, the test report will periodically update as step results are processed. In addition to generating the test report concurrently with execution, the on-the-fly Report Generator periodically persists the current test report to a temporary file. Refer to the TestStand 3.0 Reference Manual for details. When you use on-the-fly database logging, you can use the Database Viewer application to view the data in the database tables while the sequence is executing. Note that if you use this feature with a schema that uses either stored procedure or command statements that do not use the INSERT command, you cannot define constraints for foreign keys in step result statements that references primary keys in UUT results. Refer to the TestStand 3.0 Reference Manual for details. Both on-the-fly reporting and logging can be customized by the Use the Discard Results or Disable Results When Not Required By Model options on the Model Options dialog box to instruct TestStand to conserve memory by discarding results after reporting each result. In this way you can optimize the memory consumed by TestStand for each execution. TestStand 2.0.x and TestStand 1.0.x: For users of TestStand versions earlier than 3.0, there are shipping examples and the online example programs database with implementations of how to handle on-the-fly reporting and logging to databases on separate threads. Shipping examples are located in the <TestStand>\Examples directory. Refer to the Related Links section for an example program from the Developer Zone. These solutions can work in a TestStand 3.0 environment, but it is recommended that the built-in solutions be used instead. Related Links: Developer Zone Example: Setting Up Report Generation On the Fly (As You Go) for TestStand Developer Zone Example: Logging to a Database on a Separate Thread for TestStand 1.0.x Developer Zone Example: Logging to a Database on a Separate Thread for TestStand 2.0.x Attachments:
Report Date: 08/14/2003 Last Updated: 09/14/2007 Document ID: 30DB62Y6 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
