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

Set test case names in test suite (Issue #40) #43

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

Daklu
Copy link

@Daklu Daklu commented Aug 9, 2019

Implemented changes described by chrisb2244 in #40.

Functionally it works, but I didn't add setTestCaseInstanceName to the palette and I'm not sure the test package was built correctly. (The VI Tester toolbar has disappeared.)

[Edit - I branched off of Reference-Lost-Due-To-Flattening since it appears master was supposed to have been brought forward.]

Changes

Added field to Test Case:
TestCaseCtl

Added Test Case accessors:
Proj - Test Case Accessors

Added a new private file to GraphicalTestRunner.lvlib:
Proj - Get Test Instance Name

Modified Initialize Tests on Tree:
BD - Initialize Tests on Tree

jimkring and others added 8 commits February 8, 2019 22:18
* master:
  Update README.md
  Update README.md
…ue-To-Flattening

* allow-skipping-test-inside-setup:
  rebuilt package
  Improved organization of JKI SM frames to be more in line with best practices.
  Testing a change to implement vipm-io#38 (Feature Request: Allow skipping tests from setUp.vi)
  Update README.md
  Update README.md
Added testCaseInstanceName field and public accessors to TestCase class.
Added private vi Get Test Instance Name.vi to GraphicalTestRunner.lvlib.
Modified Initialize Tests On Tree.vi to use the instance name returned by
  Get Test Instance Name.vi instead of just using the class name.
@CLAassistant
Copy link

CLAassistant commented Aug 9, 2019

CLA assistant check
All committers have signed the CLA.

@kosist
Copy link
Collaborator

kosist commented Aug 21, 2020

@jimkring, let me ask you please whether there are plans in some near future to continue with VI Tester updates? Thanks a lot!

@chrisb2244
Copy link

@jimkring - Any chance this could get merged? :)

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

Successfully merging this pull request may close these issues.

5 participants