Enable automated tests to be run from VI Tester UI #55
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Nice find. Long term, I'm wondering if these should be in the other project, since that's where we expect people to spend most of their time. Regardless, this is a great improvement. |
rtzoeller
approved these changes
Oct 22, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Sets the Includes folder in
Communication Bus Custom Device Template.lvprojto be an auto-populating folder. This change enables developers to run the VI Tester tests from the VI Tester UI.Why should this Pull Request be merged?
The automated tests currently cannot be run from the VI Tester UI due to VI Tester Issue 5. To work around this, we can take egregious advantage of VI Tester Issue 33. This means the packed libraries won't be scanned when loading the UI.
What testing has been done?
Ran automated tests through UI and command line. Built and deployed on Windows.