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

Manually enter path in run window #21

Closed
compubasejovl opened this issue Jul 20, 2021 · 7 comments
Closed

Manually enter path in run window #21

compubasejovl opened this issue Jul 20, 2021 · 7 comments
Assignees
Labels
enhancement New feature or request

Comments

@compubasejovl
Copy link

It would be nice if it was possible to manually enter the path to run, and that the path entry accept the same entry as the procedure ut.run() does.
So that you could enter either the package, the test procedure or you could use the suitepath or part of it.

@simasch simasch added the enhancement New feature or request label Jul 26, 2021
@simasch simasch self-assigned this Jul 26, 2021
@simasch
Copy link
Member

simasch commented Dec 6, 2021

@compubasejovl Why do you need that because you can go to the objects browser and start the tests from there.

@compubasejovl
Copy link
Author

@simasch, thanks for you reply.

The reason is so that we could run all test from a specific suitepath. For example we have a test package with the following suitepath, "cce.tables.cce_gbr_klt_data_autorisatie.business_rules.cer0193". I know that it is possible to run part of the path, so we could run al test from "cce.tables.cce_gbr_klt_data_autorisatie" or "cce.tables", this is possible if we run the tests from plsql directly.

It would be nice to have that option in de plsql-developer plugin also, if I run the package with the suitepath from above the plugin shows the path "cce.tables.cce_gbr_klt_data_autorisatie.business_rules.cer0193", but I cannot alter is so that the plugin runs all test from "cce.tables"

I hope that it's clear why we want to have that option, if you have any questions let me know.

@simasch
Copy link
Member

simasch commented Dec 9, 2021

@compubasejovl Now it's clear. Thank you

simasch added a commit that referenced this issue Dec 10, 2021
@simasch
Copy link
Member

simasch commented Dec 10, 2021

@compubasejovl There is new release https://github.com/utPLSQL/utPLSQL-PLSQL-Developer/releases/tag/1.2.4
Would you please be so kind and test it if it fits your expectations?
If not please feel free to reopen the issue.
Thank you

@simasch simasch closed this as completed Dec 10, 2021
@compubasejovl
Copy link
Author

@simasch, thanks for the enhancement. It's exactly what I asked for.

@simasch
Copy link
Member

simasch commented Dec 15, 2021

@compubasejovl Great Thanks for the feedback!

@jgebal
Copy link
Member

jgebal commented Dec 15, 2021

@simasch
I can't find a mention of that feature in documentation (readme).
Can you add a screenshot and few words to describe that it's available and how to use it?

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

No branches or pull requests

3 participants