NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Teststand Style Sheet for sequences in XML

Hello,
 
I have a need for my colleagues who do not have a Teststand license, to view the sequences in another format.  I have found that there are ways to convert the sequence files, but I am looking for a mass update of all sequences at once since we have many sequences and it would be time consuming to convert them to html one at a time.  I used the SequenceConverterFile.exe to change all of my sequences files' format to XML.  Now if I try to open the sequence files in Internet explorer, I see what looks like an XML but without a style sheet.  Is there a style sheet that will allow me to see the sequences in XML format?    This seems like a viable option to my problem, but without a style sheet, I cannot see what the XMLs will look like.
 
April Ucci
0 Kudos
Message 1 of 11
(4,464 Views)
Hi, There is a stylesheet available for TestStand 4.0 sequence files saved in XML format.
See the following post - http://forums.ni.com/ni/board/message?board.id=330&thread.id=18543

Regards
Anand Jain
National Instruments


Message Edited by Anand Jain on 04-04-2008 10:33 AM
0 Kudos
Message 2 of 11
(4,463 Views)
Thanks, this helps a lot.  The only thing I don't see in this viewer is the ability to view the Requirements property.  We use this a lot, and we can view it in a separate column in Teststand, but I dont seem to be able to do that in this viewer.  There is no easy way to add this column, is there?
0 Kudos
Message 3 of 11
(4,448 Views)
Also, I noticed that on lines that are sequence calls, the line has both the Step name and what would be contained in the Description column.  I think the Description column should not be contained in this view, or atleast contained in another column.  It is very difficult to read.  None of the other step types contain the Description on the same line, so I'm not sure why the sequence calls are.  Also, there is a link in each of these lines where MainSequence is in purple, but when I click on them, the file cannot be found.  I checked that these files are contained within the folder I am browsing.
 
 
0 Kudos
Message 4 of 11
(4,447 Views)
One last thing about the print view.  I am finding that we do not use the Value column at all and it takes up a lot of the space on the page, which is causing some of our step names to wrap around.  Is there anyway to disable the Value column on the print screen?
0 Kudos
Message 5 of 11
(4,441 Views)

Aucci

Thank you for your feedback.

Regarding the hyperlink issue - Is the sequence file called by sequencecall step also saved in XML format?
Can you post a sample showing the issue with hyperlinks.

Regards
Anand Jain
National Instruments
0 Kudos
Message 6 of 11
(4,371 Views)

Yes that was the problem.  I did a select all and changed all my sequences to XML, but some of the ones at the end never got processed.  So the link function works now, but only the first time.  Once I click a link to see a subsequence it will show up, but then none of the other links work.  However, if I close the viewer, and reopen it, and try one of the links that didnt work, now it will work fine.

The requirements column is the most important issue that I face before I can begin to use this tool.  It would greatly help my collegues to use it, but without access to the requirements, the viewer is not useful.  A way to see this would be greatly appreciated. 

-April

0 Kudos
Message 7 of 11
(4,363 Views)
Aucci

There is a way to see requirements property - Under step properties -> 'property browser' if you expand TS you should be able to see the requirements property in the tree.
Will this work?

We are investigating if there is a easy way to display requirements for a step at a higher level in the viewer.

Regards
Anand Jain



0 Kudos
Message 8 of 11
(4,356 Views)

Hello,

Ok, I did find this now, and while at least the information is there, it would be difficult to review the sequences without the column view like it is in Teststand.  We are looking to have our test sequences reviewed by outside members, and for them to have to open this every time to see if there is a requirement for that line would be very time consuming.  I will not need the use of this tool for a couple of weeks, so if this could be resolved by then it would be a great deal better.

April

0 Kudos
Message 9 of 11
(4,351 Views)

Aucci

 This is regarding the hyperlink issue, I have been trying to reproduce the issue but I could not reproduce the error you mentioned in your post. Can you please post some more details or some sample files that help reproduce this error.

Regards
Prasanna Kumar
National Instruments

 

0 Kudos
Message 10 of 11
(4,226 Views)