Use configuration file for hardware parameters in system tests

[Karl-G1]

• [x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

• Create a shared configuration file for storing hardware parameters used in system tests
• Apply this config file to the enabled test classes

Why should this Pull Request be merged?

Fixes #66 Enable developers to override the PXI configuration (card number, BIU number, etc.) without modifying test VIs. This stores hardware parameters in Shared/Config.ini like each test class's targets.ini stores the hostname.

What testing has been done?

Ran automated tests

[niveristand-diff-bot]

Bleep bloop!

LabVIEW Diff Robot here with some diffs served up hot for your pull request.

Notice something funny? Help fix me on my GitHub repo.

Deployment.lvclass--setUp.vi.png


Deployment.lvclass--test Deployment Import BC-Only Configuration.vi.png


Deployment.lvclass--test Deployment Import Configuration.vi.png


Deployment.lvclass--test Deployment Import RT-Only Configuration.vi.png


Loopback.lvclass--globalSetUp.vi.png


[Karl-G1]

• [ ] I haven't run the tests since I don't want to interfere with other development and don't have a 1553 target, but Loopback:globalSetUp.vi seems like it's probably not using the correct config file path. The settings in the Create and Script 1553 System Definition.vi match what is in the config file, so it is likely silently being ignored. This needs to point to the Shared directory.

That sub VI should already return a path to Shared/Assets, so that logic should work. Using an invalid config file path should return error 7.

[buckd]

That sub VI should already return a path to Shared/Assets, so that logic should work. Using an invalid config file path should return error 7.

I didn't realize that scripting VI being in Shared would have that consequence.