Best practices for folder / files management with TestStand

[jungledede]

The attached "image.png" is our idea/plan.

Sequence folder is one big folder that contains all our sequences for all our test benches. It is one Git repository. (It may be split in the future to sort the sequence by test bench type).

The Wrapper folder is based on the same idea.

The Documentation is one Git repo too, but no trouble here.
Same for HMI, it is one repo, but no trouble here (only compiled code, no teststand seq file)

The sources code will be in Core (only teststand .seq files), HMI (only c# sources), Sequence (mix of teststand .seq files and source code in different languages), and Wrapper (mix of teststand .seq files and source code in different languages).

We devellop from the sequence/wrapper/core folder, but in production, the used file will be in the bin as we want the bench without source code on it ('cause it lead to modification on the line in dirty mode). Easy and no trouble for compiled files, but for teststand (and labview maybe) and the log/config folder we have an issue. We put our path from the development folder and we have not found yet an easy way to deal with the change of the main folder.

Do you have some idea/ressources to guide us ?

We are learning TestStand from 2 month to build our new test sequencer for the PG of the company (big Tier 1 supplier in automotive market). Before we got a full sequencer made in CVI, but thanks NI to drop the dev/support of CVI.

But for the HMI we will use the GRPC solution that TestStand dev team is releasing on Git Hub. Kudos for  them 🙂

[ShockHouse]

---

We devellop from the sequence/wrapper/core folder, but in production, the used file will be in the bin as we want the bench without source code on it ('cause it lead to modification on the line in dirty mode). Easy and no trouble for compiled files, but for teststand (and labview maybe) and the log/config folder we have an issue. We put our path from the development folder and we have not found yet an easy way to deal with the change of the main folder.🙂

---

I may be missing part of what you are doing. But we do a similar thing where I work with separate source and deployed code. What you want to make use of here is Search Directories. Your deployed machines can have different search directories pointing to the bin folder, whereas your development machine can have search directories pointing to the source. As long as you use relative paths in your sequences, that is all it should take to change where they look.