Database Options Dialog Box

TestStand 2019 Help

Edition Date: May 2019

Part Number: 370052AA-01

»View Product Info
Download Help (Windows Only)

Logging/Data Link Options Tab

Logging Options Section

The Logging Options section of the Logging/Data Link Options tab contains the following options:

  • Disable Database Logging—Enable this option when you do not want TestStand to log data to a database.
  • Use On-The-Fly Logging—Specifies whether TestStand logs to a database after testing a UUT, or logs concurrently with the execution. When you enable this option, the process model uses Post Result callback sequences to process new results. When you disable this option, database logging occurs after the testing of each UUT completes.
    Notes Notes
    • If you attempt to use on-the-fly database logging with a schema that uses stored procedure statements or command statements that do not use the INSERT command, you cannot define constraints for foreign keys in step result statements that reference primary keys in a UUT result statement or foreign keys in a step result statement that references its own primary keys. When you define constraints for these types of foreign keys, an error will occur because the on-the-fly database logger cannot execute the statement to create the record that contains the primary key before executing the statement to create the record that contains the foreign key.
    • The Generic Recordset (NI) and TS 2.x—4.0 Generic Recordset (NI) database schemas use the TOP 1 clause in the command text for all statements, as the following example shows, to improve performance when logging results to a database by preventing the recordset from accessing existing records in the database:

      SELECT TOP 1 * FROM <TABLE NAME>

      This performance improvement is useful when you enable the Use On-The-Fly Logging option for database files larger than 500 MB.
  • Include Execution Times—Enable this option when you want to log the total step execution time and the time each code module takes to execute.
  • Use Transaction Processing—Instructs TestStand to begin a transaction operation before logging each UUT result and commits the transaction operation after logging the UUT results. If TestStand fails to log results for a UUT, TestStand rolls the transaction operation back to prevent the partial results from being logged. This option is not available when you enable Use On-The-Fly-Logging in the Logging Options section.
  • Include Step Results—Enable this option when you want to log the results of each step. Disable this option when you only want to include information about each UUT you test.
  • Include Measurements—Enable this option when you want to log the measurement values steps acquire. The default schemas recognizes specific step properties as containing values to log. These include properties such as Result.Numeric, Result.String, and Result.Measurement. For the Numeric Limit Test built-in step type, Result.Numeric contains the numeric measurement the step acquires. For the String Value Test built-in step type, Result.String contains the measurement value the step returns in string form. For the Multiple Numeric Limit step type, Result.Measurement[].Data contains the numeric measurements the step acquires.
  • Include Test Limits—Enable this option when you want to log values step types use as test limits. The default schemas recognize specific step properties as containing test limits. These properties include Limit.Low, Limit.High, Limit.String, and Comp. The Numeric Limit Test compares the measurement value it acquires against Limit.Low, Limit.High, or both, and uses Comp to select the type of comparison to make. The String Value Test compares the string it acquires against Limit.String and uses Comp to indicate whether to ignore the case in the comparison.
  • Result Filtering Expression—Specifies which step results appear in the database by specifying an expression the database logger evaluates for each step result. The database logger includes the step in the database if the expression evaluates to True. You can use any subproperty in the Result property of the step, but you must use Logging.StepResult in place of Step.Result. For example, if you want to include only failing steps in the database, set the expression to Logging.StepResult.Status == "Failed". You can use the ring control to the right of the Result Filtering Expression control to select one of the following predefined expressions:
    • All Results
    • Exclude Passed/Done/Skipped
    • Passed/Done Only
    • Exclude Flow Control
    Open the Expression Browser dialog box, in which you can build the expression by clicking the Expression Browse button.

See Also

Expression Browser dialog box

WAS THIS ARTICLE HELPFUL?

Not Helpful