Something Like Mass Complie?

[Bob_Y.]

Is there something that I can do to my TestStand sequences that will force them to check all of the links to other code?  I am looking for all of the calls to LabVIEW VIs and external C to be checked for correct path and parameters.  I would like to have a report of all of the failures and maybe even have some of them fixed.  I am thinking that this would be similar to LabVIEW's mass compile tool.

I am really tired of only finding problems by running the sequences.  I want to check them first and only have run problems be actual coding mistakes.

Since my TestStand education is lacking (mainly self taught), it might be right there somewhere and I just don't know what it was called or where it is.  If not, does anyone have any tools that they use to ensure that they have all of their ducks in a row?  Any suggestions?

Thanks,
Bob Young

[SercoSteve]

Hi Bob

Try 'Deploy TestStand System' from the Sequence Editor Tools menu.  You will need to create a TestStand Workspace file, that contains the sequence you want to check.  Once that workspace is selected click the Distributed Files tab and then Analyse Files.  The application builder will give you a list of all VIs called by the sequence. 

I have not done this sort of thing with external C but I'd guess it will give you the same sort of response.

Hope this helps

Steve

Message Edited by SercoSteve on 03-09-2006 06:04 AM

[Bob_Y.]

SercoSteve,

We're getting there, but it doesn't really help me get what I am looking for.  I want to have a tool that goes through each sequence in a workspace and finds all of the broken links, changed prototypes, and bad parameter values.  I see where what was suggested would have value in making sure that you have all of the files.  But, I need to have a bit more help :-). 

I started out with a few VIs that had three inputs, but decided later that I need to add a fourth.  Therefore all of the previous uses of this VI are errors.  Ocassionally I need to move a file.  Therefore all of the previous uses of this file will not find it where it used to be and so they have errors.  And once I changed a VI control's datatype from a string to an enum.  Therefore all of the previous uses of that VI have an error.  I am looking for a good way to have TestStand check for all of these errors and report them to me. 

I did not see any of this from the tool suggested (unless I did something wrong, which is quite possible).

Any other suggestions?

Thanks,
Bob Young

[SercoSteve]

Bob

If you continue on and do a 'Build' using the TestStand Deployment Utility it will tell you which VIs are broken, but it wont give you the sort of details you're looking for. At least you'll know which VIs to look at though.

If you find a more detailed analysis tool, can you post its info here.  I could find a use for a tool like that

Regards

Steve

[Mike_T]

Here is a VI that I wrote that parses the sequence and returns all the VIs called.  This is part is a bigger tool I wrote to ensure when I released software I released all files needed.  Once you get all the names you can use another tool to see if they are broken, missing, etc.  Not sure how to see if the parameters have changed.  But this example shoud get you started.  I also trigger a warning if the VI is a called from a relative path.  This bit me one too many times, so I want to know if the path is relative or not.

VI written in LV 7.1

Mike T.

DZine Technologies

http://dzinetech.com/