Allow tests to work on multiple RT platforms using a configuration file #52
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this Pull Request accomplish?
Introduces the notion of a
targets.ini
file that can be specified per test-class. This file is applied after the overrides, and supports changing the target operating system and hostname.The file format is shown below for a test class supporting PharLap and Linux on PXI.
Why should this Pull Request be merged?
To enable running tests on multiple OSes automatically, we want to be able to configure the OS and IP address used by all system definitions in a test class through a single configuration file. By standardizing the name and relative location of this file, we can easily map test classes to configuration files, which is not true today.
The ATS will subsequently be updated to modify the active configuration and hostnames in the
targets.ini
files during test runs, to iterate through all supported targets.What testing has been done?
Ran unit tests in the repository.
Updated the NI Synchronization system tests to use the new format and confirmed that they deployed to the correct target, based on the active configuration.