10 results found
-
0 votes
-
Always show Requirement title
We link 'commenter' users to a requirement with this link (sans /edit/)
https://prod.practitest.com/p/xxxx/requirements/xxxxx/
This provides a nice read-only view of the req. The problem is that the req title does not appear anywhere on the page, only the description and other fields.
Pls always display the requirement title on this page.
3 votes -
Remove auto filter limitation
Support the option to create more than 50 auto filters per module
0 votes -
Support for auto filters for more than 2 levels
Allow to create auto filters on more than 2 levels
0 votes -
Provide ways to Archive Dashboards in PractiTest
Hello,
Currently, there are no ways to Archive Dashboards in PractiTest. As a matter of urgency, please implement ways to Archive Dashboards in PractiTest?For instance, some Teams on a 2-weeks per month Sprints would like to never delete their Dashboards, but keep them for future references to their Leadership team's consumption.
Without a Dashboard Archive feature in PT, the number of dashboards will go pretty fast; and will become difficult for the QA teams and their Leadership teams to navigate.
PT Team, please consider implementing Archive Dashboards feature in PractiTest.
Thank you!
Best regards,
FelixBest regards,
Felix2 votes -
include the ability to add tests all at once instead of individually when adding tests on the traceability tab in requirements.
We often add 10 or more test cases to each requirement which means having to click "Add" that number of times to link each test case. It would be nice if there was a way to add all of them at once.
1 vote -
Please provide option to link Test set with Requirement.
Please provide option to link a Test Set with a requirement. As of now we have to link one by one all the test cases for a requirement and its time consuming when we have big projects with 300+ test cases.
67 votes -
Ability to sync the comments from requirements and bugs from ADO to PractiTest and vice versa
Currently when the requirements and bugs are synced from ADO, the comments are not synced.
For requirements the comments have valuable information reflecting the changes and doubts which are important for a tester to know while creating test cases so it is very critical to include the comments as well.Also if a tester has certain doubts on a requirements if there is a 2 way sync he can just post the comments on the PractiTest and they should flow to the linked requirement card in the ADO.
For bugs, since the developers won't always have access to PractiTest, the will…
28 votes -
Reviewing Test Cases Support
Is there a way of making reviewing test cases easier?
We can mark the tests ready for review, but would be easy if we have some GUI support to add the review comments to the steps or description.
We don't have to rely on other tools to send review comments etc if it is supported in PT itself.
17 votes -
Add Collision detect on Test edition
We have encountered situation when I have edited the Tests while my colleague had it open and editing. I have saved the changes first and when he saved his, mine were lost. It is quite a big problem in distributed large teams. Please take a look.
5 votes
- Don't see your idea?