NI TestStand

Showing results for 
Search instead for 
Did you mean: 

TestStand Project Folder Structure

Hi to all


Is there a Guideline or best practice for the Folder structure for a TestStand Project.

I have a Project with a lot of Sub-Sequences and external Libraries and I don't know whats the best way to organize them.


What is your best approach?


Best regards

0 Kudos
Message 1 of 5

Generally speaking…. Your main sequence file on toplevel, all dependencies in folder underneath.

This also leads to a very lean search directory structure 



At least that’s what I recommend 


are you using a TestStand Workspace?

0 Kudos
Message 2 of 5

Sometling like below works for me:








key is to have all referenced as relative paths so when You deploy/move folder all works.

Message 3 of 5

Thanks for your answers


For me it is not clear where to place the code Modules for the subsequnces and how to deal with it when you have a code Modules used in more than one subsequnce?


Best regards

0 Kudos
Message 4 of 5

I tend to put most of my library folders on the same file hierarchy level.


If they refer to each other, they only need to "jump up a folder" and "jump in" the appropriate other.


BTW.... using a TestStand Workspace can also help.


0 Kudos
Message 5 of 5