The following sections describe the built-in TestStand rules.
|Expressions must evaluate to a value of the expected type
||Each expression property must not include syntax errors and must evaluate to a value of the type
the property expects. Syntax errors and incorrect value types can cause errors at run time.
If you are certain that the expression will evaluate correctly at run time, such as when you dynamically
create variables or when you propagate variables, use the #NoValidation directive in the expression
to suppress the error.
|Step properties must have valid values
||All step properties must have valid values. Invalid property values can cause errors at run time.
Use the Step Settings pane to set the property to a valid value. Ignore this message if the property
will be set dynamically to a correct value at run time.
|Files must be found on disk
||File paths must refer to existing files on disk. TestStand can report errors at run time if it cannot
find the file the path specifies. Correct the problem by correcting the path or by creating
the file on disk. You can safely ignore this message if the file is created dynamically at run time.
|Files should be found on disk
||File paths should refer to existing files on disk. TestStand does not report errors at run time for
these files, but the path specified cannot be found. Correct the problem by changing the path to point to the correct
file or by creating the file on disk. Ignore this message if the file is created dynamically at run time.
|Code modules must be able to load
||TestStand must be able to load all code modules without error. TestStand reports errors at run time when it
cannot load a code module. Correct this problem by editing the step in the sequence editor.
|Code modules should load without warnings
||TestStand should be able to load all code modules without warnings. Module load warnings are issues
that occur when trying to load a code module that might or might not be fatal or cause unexpected behavior.
Correct this problem by editing the step in the sequence editor.
|Code modules must have expected prototype
||The prototype for the code module must match the prototype the step module specifies. TestStand reports
errors at run time when it loads a code module with an incompatible prototype. Correct the problem
by editing the step module in TestStand to match the code module or by changing the code module prototype
to match the step module.
|Remote computer must be on the network
||Step properties that refer to remote computers must specify a valid network computer by IP address or by computer name.
Ignore this message if the computer will exist at run time.
|Steps must have expected block structure
||Steps with block structures, such as the Flow Control steps and the Auto Schedule step, must have matching
End steps, and End steps must have a matching Begin step. Other block requirements exist for Select/Case
and Auto Schedule/Use Auto Scheduled Resource steps. TestStand reports errors at run time for invalid
|Variables should be used
||Unused variables and parameters add unnecessary complexity and extraneous information to sequence files.
Delete variables if you never access them. You can ignore this rule for variables that you access
in code modules or that you access using a lookup string with the TestStand API.
|Sequences should be used
||Unused sequences add extraneous information to sequence files and needlessly increase the size
of the file. Delete sequences if you never use them. You can ignore this error for sequences that you call
by expression or if you call the sequence from a sequence file that was not analyzed.
|Steps should have Normal run mode
||The run mode option for step should be set to Normal instead of Force Pass, Force Fail, or Skip to ensure that tests are performed correctly. Correct the setting on the Run Options Panel of the Step Settings pane in the TestStand Sequence Editor. Ignore this message if a step is intentionally set to this run mode.
|Sequence calls should match the sequence prototype
||The prototype for the sequence that a sequence call step calls should match the prototype
the step specifies. You can ignore this rule for sequence calls in which you intend to pass a different
set of parameters and if you check the parameters in the called sequence.
|Find file paths that expressions specify
||Files that path expressions reference might not be included in the set of files to analyze.
This rule provides a list of those expressions. You might need to manually add files expressions
reference to the workspace for correct deployment.
|All escape sequences used in expressions must be valid
||The sequence analyzer checks expressions for valid escape sequences. Improperly escaping
paths usually leads to using invalid escape sequences, which are rarely intended.
|Expression error caused by missing dynamic property
||Expressions that use dynamic properties, such as RunState, will evaluate with errors at edit time.
Ensure that the variable referenced will exist at run time. This message occurs when
an expression evaluation error occurs because of a missing variable that starts with RunState
or Parameters and the parameter is a container or object reference. If this variable
will exist at run time, you can safely ignore this message.
|Types should have the correct version
||Ensure that all types have versions that will not conflict with the default versions TestStand installs. This
message can occur when you have a copy of CommonResults that is less than 188.8.131.52. National Instruments recommends that
you set the version of CommonResults to the default of 184.108.40.206 if it contains no subproperties and set the version of CommonResults greater than 220.127.116.11 if it
contains subproperties. Failure to change the version might cause type conflicts when loading files.
|Steps that call LabVIEW modules configured with LabVIEW 7.1.1 or earlier should reload module prototypes
||The prototype information stored on steps that call LabVIEW code modules might not be compatible with LabVIEW 2012 or later.
This warning occurs for a step that calls a LabVIEW code module and the step was last configured using LabVIEW 7.1.1 or earlier.
The step calls the code module correctly, but TestStand might generate an error when executing the step using LabVIEW 2012 or later. National Instruments recommends that you reload the prototype for the step or select Tools»Update VI Calls to run the Update VI Calls tool on any sequence file that return this warning.
|Delete subelements of an output array parameter if you intend to log the entire array
||If you enable additional result logging for an output array parameter on a LabVIEW or .NET step and the parameter contains subelements,
the step logs only the subelements and not the entire array. An array parameter contains subelements if you added them manually when
you specified the code module or if the code module is a LabVIEW VI that defines default element values for the array. To log the
entire array, delete all the parameter subelements when you specify the code module. Ignore this message if you intend to log only
the parameter subelements.
|Find expressions that suppress evaluation errors
||Expressions that use the #NoValidation directive to suppress semantic evaluation errors
might contain actual run-time errors.
|Disable result recording for all process model sequences except the MainSequence callback
||If you enable result recording for a process model sequence other than the MainSequence callback, On-The-Fly reporting might not work
correctly. Disable result recording for all process model sequences except the MainSequence callback.