Quantcast
Channel: NI TestStand topics
Viewing all articles
Browse latest Browse all 6736

Best practices for development/deployment

$
0
0

Hello,

I'm returning to TestStand after a few years and a lot of learning about software engineering. When I worked with TestStand in the past, quite a lot of the dev/deployment environment was poorly controlled. For instance, it seems like the report options are kept in AppData at "C:\ProgramData\National Instruments\TestStand 2025 (64-bit)\Cfg\ModelPlugins" so they're global to the station and need to be protected from edits.

 

Ideally I would like to specify all the options that affect how my test executes and records data within the same git repo containing the sequences and module code, such that when I go to deploy all that stuff is included, and when the next developer opens the project they will deploy the same thing as when I deploy it. Generally I see 3 ways to do this on cursory inspection:

  • Override all options from my sequence using callbacks (ReportOptions, ModelOptions etc)
  • Keep "canonical" config files in git and automatically copy them over at some point
  • Keep process model for my sequence in git and force it to be used, and edit it so it does not use global config files

Any options I'm missing? What's the "standard" approach to keep everything repeatable across environments?


Viewing all articles
Browse latest Browse all 6736

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>