Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open Tests Associated with Current VI #90

Open
jacobson3 opened this issue May 21, 2020 · 3 comments
Open

Open Tests Associated with Current VI #90

jacobson3 opened this issue May 21, 2020 · 3 comments

Comments

@jacobson3
Copy link

This is more of an "idea exchange" type post with a small PoC. I thought that it might be interesting to be able to work on a VI for your application and easily navigate to the the associated tests for that VI. The concept would be that you are working on "Parse Message Data.vi" and by just invoking a QD shortcut, the VI used for testing that VI pops up.

Attached is a super basic proof of concept built in LabVIEW 2019. If the VI is put in the QD plugins folder you can use the Ctrl+A QD shortcut to open the first "Test VI" found where a test VI is determined by being a VI in your active project which links to both the Define Test Caraya VI and the VI which makes the QD call.

Most of the functionality needed to do this already exists in "Test Runner.Project.lvclass:onTestDiscovery.vi". The attached code is mostly just inlines existing functions so everything is on one VI and to avoid scoping issues.

QD.zip

@jimkring
Copy link
Contributor

Hi @jacobson3. This is a fantastic idea and a very valid/common use case! It gets my vote.

@jacobson3
Copy link
Author

Thanks Jim. I think the biggest open question would be how to handle instances where multiple tests call the VI in question. If one test is found I think you can just open the VI directly but if multiple tests are found, a dialog similar to the choose class implementation preview should come up.

@jimkring
Copy link
Contributor

jimkring commented May 22, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants