Saving custom queries for test cases
Hi,
I'm trying to setup a custom query of available test cases in a test plan to later add it to the 'Test artifact' widget. I'm following this article.
If I browse for Test Plans and I expand the inline filter area I can see the save icon. However, if I select a Test Plan and then its Test Cases, expanding the inline filter area doesn't show me that save icon.
I'm using RQM 5.0.2 but I've tried it also in a jazz.net sandbox with 6.0.0 with identical results. Am I missing something?
Thanks and regards
Oskar
I'm trying to setup a custom query of available test cases in a test plan to later add it to the 'Test artifact' widget. I'm following this article.
If I browse for Test Plans and I expand the inline filter area I can see the save icon. However, if I select a Test Plan and then its Test Cases, expanding the inline filter area doesn't show me that save icon.
I'm using RQM 5.0.2 but I've tried it also in a jazz.net sandbox with 6.0.0 with identical results. Am I missing something?
Thanks and regards
Oskar
One answer
Hi, Oskar
The query creation is only available through artifacts view(such as test plan, test case etc) currently and that's why the embedded view within an artifact can only filter with the conditions but not able to save it.
There is enhancement for what you are after and you may want to vote for it.
Save testcase query within test plan
thanks
The query creation is only available through artifacts view(such as test plan, test case etc) currently and that's why the embedded view within an artifact can only filter with the conditions but not able to save it.
There is enhancement for what you are after and you may want to vote for it.
Save testcase query within test plan
thanks
Comments
Hi Don,
Thanks for your answer. How do I vote for that enhancement?
Regards
Oskar
Hi, Oskar
RQM WI does not seem to have 'vote' feature. you can add your comments to the RFE with your intention and justification of having that feature. In general, more users want to have that feature, the higher possibility to get implemented.
Thanks