Add skip output from OpenVeriStandConnection so additional code in se…

[buckd]

…tUp.vi can be ignored

• This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

Allows code in test cases using OpenVeriStandConnection.vi to know if the open was skipped so additional code in setUp.vi can be ignored

Why should this Pull Request be merged?

Even if a test is skipped because the minimum version requirement is not met, the rest of the code in setUp.vi will still execute. If an error occurs in that code, the test will show up as failed instead of skipped.

What testing has been done?

Used skipped output to conditionally execute setup code that will error if not skipped.

[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.

The following VIs could not be diffed:

• C:\jenkins\workspace-device-testing-tools_PR-35-5QAO3GDN67BEMHVKBOLBXIHFA4FOVNTZYX4ISQBGG2XKEEX66WKQ\VeriStandTestCase\OpenVeriStandConnection.vi

[rtzoeller]

I think the diff bot failed because renaming the old VI for diffing is detaching it from the class. Need to investigate possible fixes. Will review manually.

[rtzoeller]

@buckd does it make sense to expose this as a getter instead? I am imagining calling this in setUp.vi, and needing to change my tearDown.vi logic to do less if the test was skipped.

[buckd]

does it make sense to expose this as a getter instead?

Then we're back to re-implementing a field that already exists in VI Tester, but isn't exposed publicly. So far, I haven't really had to change anything in cases where we've skipped. For the case that prompted this particular change, I can just ignore a specific error on close of the bitfile.