I am the architect for a project that uses TestStand, Switch Executive and LabVIEW code modules to do automated testing on a number of UUT's that we make.
This is my first time using TestStand and I want to adopt software best practices by enabling code sharing between my other software engineers who will each be responsible to create TestStand scripts for one of the many unique UUTs. I've identified certain "functions" that will be common across all the UUTs such as connecting two points on our switch matrix and then taking a voltage measurement with our SMU to check if it's within limits.
The gist of my question is what is TestStand's version of a LabVIEW library for sequence calls?
Right now what I've done is create these common/generic sequences using parameters and placed them in their own sequence file called 'Common Functions.seq' as a pseduo library. This 'Common Functions.seq' file is never meant to be run as a script itself, rather the sequences inside are called into by another top-level sequence that is unique to one of our UUTs.
Is this a best practice or is there a better way to compartmentalize common sequence calls?