Remove skip test field #34
Merged
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
VI Tester added a feature in version 3.0.2 to allow skipping from setUp.vi.
1 task
rtzoeller
approved these changes
Feb 27, 2019
|
Please bump the required version of VI Tester in the README |
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.
VI Tester added a feature in version 3.0.2 to allow skipping from setUp.vi.
What does this Pull Request accomplish?
Remove duplicate fields for determining whether to skip tests or not.
Why should this Pull Request be merged?
The field in VeriStandTestCase is now useless.
What testing has been done?
Ran Engine Simulation tests that use skipping logic.
2019_02_27_08_03_31 VI Tester.txt