Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Is there a way to read the version of a TestStand sequence file which is under source control?
Bob Rafuse
Member
07-13-2001 04:00 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
We've just started evaluating TestStand 2.0 and I have a question regarding
its support for source version control:
Is there a "built-in" way for a sequence (or a DLL that uses the TestStand
ActiveX API) to programmatically determine the version of a sequence file?
One of our requirements is that there is a central database which contains
the current "approved" versions of various sequence files (stored by name).
Ideally, we'd like to be able to prevent a user from inadvertently running
an out of date version by comparing the version of the sequence file they
are running against the sequence file name's entry in the database at
runtime.
Is this possible with a
ny built-in TestStand mechanism?
Bob Rafuse
Etec Inc.
its support for source version control:
Is there a "built-in" way for a sequence (or a DLL that uses the TestStand
ActiveX API) to programmatically determine the version of a sequence file?
One of our requirements is that there is a central database which contains
the current "approved" versions of various sequence files (stored by name).
Ideally, we'd like to be able to prevent a user from inadvertently running
an out of date version by comparing the version of the sequence file they
are running against the sequence file name's entry in the database at
runtime.
Is this possible with a
ny built-in TestStand mechanism?
Bob Rafuse
Etec Inc.
rpfi
NI Employee (retired)
07-16-2001 04:41 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hello Bob,
In TestStand, the sequence file version is stored in RunState.SequenceFile.Data.Version. As far as I know, there is no "Built-In" method of preventing one sequence to be executed according to the sequence version. However, it is not complicated to create this functionality. You may modify the process model in order to query the database (using database step types) for the approved version and if it doesn't match with the property mentioned above, you may jump to the "END" (using a goto step).
If you don't want to change the process model, you may modify your sequence instead of the process model. In this case, you may include in the "Setup" Step Group, database steps to query your database and jump to the END if the versions don't match.
Robert
o Piacentini
National Instruments
In TestStand, the sequence file version is stored in RunState.SequenceFile.Data.Version. As far as I know, there is no "Built-In" method of preventing one sequence to be executed according to the sequence version. However, it is not complicated to create this functionality. You may modify the process model in order to query the database (using database step types) for the approved version and if it doesn't match with the property mentioned above, you may jump to the "END" (using a goto step).
If you don't want to change the process model, you may modify your sequence instead of the process model. In this case, you may include in the "Setup" Step Group, database steps to query your database and jump to the END if the versions don't match.
Robert
o Piacentini
National Instruments
07-17-2001 08:00 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
> In TestStand, the sequence file version is stored in
> RunState.SequenceFile.Data.Version. As far as I know, there is no
> "Built-In" method of preventing one sequence to be executed according
> to the sequence version. However, it is not complicated to create this
> functionality.
Sorry, I meant "built-in" meaning method to read the version. Looks like
its there. I have no problem adding the checking code to the process model.
Thanks!
Bob Rafuse
Etec Inc.
> RunState.SequenceFile.Data.Version. As far as I know, there is no
> "Built-In" method of preventing one sequence to be executed according
> to the sequence version. However, it is not complicated to create this
> functionality.
Sorry, I meant "built-in" meaning method to read the version. Looks like
its there. I have no problem adding the checking code to the process model.
Thanks!
Bob Rafuse
Etec Inc.
John_Morrissey
Member
08-07-2001 12:19 PM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Does this variable (RunState.SequenceFile.Data.Version) exist in TestStand 1.0.3? I was unable to access it.
rpfi
NI Employee (retired)
08-08-2001 11:20 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report to a Moderator
Hello John,
Unfortunatelly there is no version information on TS 1.0.3. SCC was introduced in TS 2.0. However, you can implement it on your files. Basically you can create a sequence file global to store the version, so all the sequences in this file will have access to this property.
Roberto Piacentini
Applications Engineer
National Instruments
www.ni.com/support
Unfortunatelly there is no version information on TS 1.0.3. SCC was introduced in TS 2.0. However, you can implement it on your files. Basically you can create a sequence file global to store the version, so all the sequences in this file will have access to this property.
Roberto Piacentini
Applications Engineer
National Instruments
www.ni.com/support
