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

Custom TestCase Templates #2

Open
nephe opened this Issue May 9, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@nephe

nephe commented May 9, 2017

Hi,
It would be nice to have an option to add custom test case/suites templates from menu or using VI tester GUI. Right now there is only option to add the ones provided with VI tester.

@kosist

This comment has been minimized.

Show comment
Hide comment
@kosist

kosist Apr 9, 2018

Contributor

This could solve issue #20 .
I guess implementation could be quite simple.
While adding new Test Case, there could be window with:
image

  • Test Case Name;
  • checkbox "Save to Project Folder?" (default: selected). If selected, then test case will be saved to root folder of the project, into the created folder. If not selected, then dialog window will appear to select folder to save test case;
  • path control "Test Case Template". And then:
    If it is empty, then no template is used (but default one).
    If it is not empty, then toolkit checks, if class is child of "TestCase.lvclass".
    If yes, then it'll be copied and used as template.
    If it is not in hierarchy of "TestCase.lvclass", then it will be not used (and promted to user) OR it could be set as child of "TestCase.lvclass".
    If it is in hierarchy of "TestCase.lvclass", but not its "direct" child, then possible to use it, but change inheritance to "TestCase.lvclass" OR copy it with all its parents hierarchy. This is something what I'm not sure...

Will it be OK, please @jimkring ? Could it be implemented like that?

Contributor

kosist commented Apr 9, 2018

This could solve issue #20 .
I guess implementation could be quite simple.
While adding new Test Case, there could be window with:
image

  • Test Case Name;
  • checkbox "Save to Project Folder?" (default: selected). If selected, then test case will be saved to root folder of the project, into the created folder. If not selected, then dialog window will appear to select folder to save test case;
  • path control "Test Case Template". And then:
    If it is empty, then no template is used (but default one).
    If it is not empty, then toolkit checks, if class is child of "TestCase.lvclass".
    If yes, then it'll be copied and used as template.
    If it is not in hierarchy of "TestCase.lvclass", then it will be not used (and promted to user) OR it could be set as child of "TestCase.lvclass".
    If it is in hierarchy of "TestCase.lvclass", but not its "direct" child, then possible to use it, but change inheritance to "TestCase.lvclass" OR copy it with all its parents hierarchy. This is something what I'm not sure...

Will it be OK, please @jimkring ? Could it be implemented like that?

@JamesMc86

This comment has been minimized.

Show comment
Hide comment
@JamesMc86

JamesMc86 Aug 7, 2018

I think it would be better if it could be part of the context menu.

New Test >> Standard Template
New Test >> Wiresmith Template

etc. More complex installation but better developer experience.

JamesMc86 commented Aug 7, 2018

I think it would be better if it could be part of the context menu.

New Test >> Standard Template
New Test >> Wiresmith Template

etc. More complex installation but better developer experience.

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