Test Failure Dialog Box To Retry, Break, or Continue (TestStand 1.0.x)
PrintDownloads
Filename: poststepcallback-labview.zip
Requirements: View
Filename: postaction-labview.zip
Requirements: View
Filename: postaction-labview60.zip
Requirements: View
Filename: postaction-cvi.zip
Requirements: View
Filename: poststepcallback-labview60.zip
Requirements: View
Filename: poststepcallback-cvi.zip
Requirements: View
These examples demonstrate how to handle test failures. The two main differences between the examples are as follows:
The PostAction examples only handle step test failures when you have properly configured the Post Actions of the step.
The PostStepCallback examples handle step test failures for all steps in your sequence file.
In addition, the PostStepCallback examples incur a little more run-time overhead because the SequenceFile PostStep callback sequence is called after every step in your sequence file. In contrast, the PostAction examples require more development time and knowledge because the sequence developer must configure each step on which the step test failure should be applied. It is possible to create a TestStand tool that programmatically modifies the Post Actions of selected steps.
Note: The attached examples are designed for TestStand 1.0 .x. Although these examples work in TestStand 2.0, there are better solutions. Refer to the shipping example in your TestStand installation at
Note: Attached are files written in LabVIEW 6.0 as well as files for earlier versions.
Requirements
Filename: poststepcallback-labview.zip
Software Requirements
Application Software: NI TestStand Development System 1.0, LabWindows/CVI Full Development System 5.0, LabVIEW Full Development System 5.1.1
Language(s): LabVIEW, C
Software Requirements
Application Software: NI TestStand Development System 1.0, LabVIEW Full Development System 5.1.1, LabWindows/CVI Full Development System 5.0
Language(s): LabVIEW, C
Software Requirements
Application Software: NI TestStand Development System 1.0, LabVIEW Full Development System 6.0
Language(s): LabVIEW
Software Requirements
Application Software: NI TestStand Development System 1.0, LabVIEW Full Development System 5.1.1, LabWindows/CVI Full Development System 5.0
Language(s): LabVIEW, C
Software Requirements
Application Software: LabVIEW Full Development System 6.0, NI TestStand Development System 1.0
Language(s): LabVIEW
Software Requirements
Application Software: NI TestStand Development System 1.0, LabVIEW Full Development System 5.1.1, LabWindows/CVI Full Development System 5.0
Language(s): C, LabVIEW
Reader Comments | Submit a comment »
Contain more functionality than i need (Abort
and break) but that i easily remove.
Missing feature 1:
If i want to retry the test then i also would
like to remove the previous test result. I
just do it by removing last element from
Runstate.caller.locals.resultlist
Missing feature 2:
I do not want this callback on all tests. I
have made a extra Boolean named UseCallback
in the Standard data type CommonResults which
turns on the callback functionality for a
specific step.
- Rolf østvik - Jun 3, 2003
Legal
This example program (this "program") was developed by a National Instruments ("NI") Applications Engineer. Although technical support of this program may be made available by National Instruments, this program may not be completely tested and verified, and NI does not guarantee its quality in any way or that NI will continue to support this program with each new revision of related products and drivers. THIS EXAMPLE PROGRAM IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND AND SUBJECT TO CERTAIN RESTRICTIONS AS MORE SPECIFICALLY SET FORTH IN NI.COM'S TERMS OF USE (http://ni.com/legal/termsofuse/unitedstates/us/).