92 results found
-
add the ability to duplicate filters
it would be very useful if we can duplicate the filters (instead of re creating them every time ) in case we need them in several places.
70 votesWe are not currently planning to add this feature. Instead, we recommend to use our Auto Filters, which now have an additional hierarchy level and soon will be available for Multi List and Linked List types of fields.
With the Auto Filters, you'll be able to organize your data using Filter trees with less effort . -
Creation of filter via the API
We want to be able to create filters from the API
this will allow us to group text sets created via a pipeline and better organize what tests where ran where64 votesOur Auto Filter feature (now with an additional hierarchy level) will ensure that a new filter will be automatically created for every new value of a List field, even if added via API.
-
Add the ability to view Test Steps directly from Test Sets
Now, the only thing we can do to view Test Steps from Test Sets is by:
1. Clicking the instance
2. Click "Test in Test Library"which means we can only see steps for a particular test at a time.
I'd suggest that you add the ability to view Test Steps directly from Test Sets, maybe by implementing display popover? Or maybe add another page that allows us to view all steps in all the tests in a certain test set. Thanks!
41 votesThis request has been rejected since it does not make sense from a methodological point of view.
-
Link test to test
Please make it possible to link test cases between each other
40 votesWe have not found a justification for this request.
-
Save search as filter
Add ability to convert a search to a filter (which can be later customized).
39 votes -
Allow to select from used tags when entering Tag as filter criteria
When creating filters and tag is selected as filter criteria - choose from list of used tags (select with search) to avoid spelling mistakes
39 votesThis request is not in our current roadmap.
-
Import Jira requirement ticket with all it's sub-tickets
In order to provide better coverage of the specifications I do propose to implement:
- Tree-like import that means importing parent and subtickets;
- Provide straight dependence between subticket and linked test, i.e. if Practitest user link test to subticket the test should also be linked to parent ticket automatically, as subticket is a must part of parent;
- Add system field "Traceability" for requirements that will reflect clickable test IDs;
If the solution will be implemented it will simplify test covering process and test covering tracking process;
28 votes -
Add "+" and "-" for edited test case in history log
It would be better to see the changes in the test case history log when the test was updated by adding "+" (for addition) and "-" (for removal) signs in front of each change
27 votes -
option for cloning traceability (linking between requirements and tests)
Whenever I need to clone Tests or Requirements I have to do double work of adding back linking between entities an option for cloning not only attachments but also linking between Requirements and Tests would help.
26 votes -
Suggestion on the "Call to test" feature
The feature "Call To Test" brings some limitations to us. I want to see if your team can provide some solutions or improvement plan. Thanks you!
- No tracability between parent test cases and the called tests
- Tester is difficult to trace the relationship between parent and the called test
- Cannot preview the called test steps in the test cases. The test case only show the title of the called tests
- It's time consuming to open the new tab to view cases one by one
- Suggestion: Preview by clicking a button
- Export test cases: Test cases exports with only the title…
24 votes - No tracability between parent test cases and the called tests
-
2 way integration with GitLab would be a nice feature.
Many companies use GitLab and they would warmly welcome a 2 way PT integration. At our company we conclude projects. One is developed in Redmine, the other is in GitLab. It would be nice to use PT for both platforms with equal funcionality.
22 votes -
Create the ability to import parameters
Rather than having to copy and paste parameters in from a datasheet, it would be good if we could map the parameters for multiple instances of a test case to a datasheet and import them
eg Select 10 instances of a test case, click an 'bulk update parameter' button or similar, which can then map to an excel datasheet22 votes -
Reorder TestCases in Test Library
The user should able to sort the TestCases for a project in the Test Library.
This will be easier for us enduser to make a TestSet that have the same type of testcases in a row.
20 votesHi,
Thanks for your feature request.
In PractiTest we strongly recommend customers to use Custom Filters (https://www.practitest.com/help/settings/custom-filters/) that allow to sort information in every module: the Requirements module, the Test Library, the Test Sets & Runs module and the Issues module.
Also we allow to add all tests residing under a specific filter to a Test Set.
Best regards,
Christine -
Autosave any change while editing
When working on browser it's always good to have Auto Save feature. you can by mistake click on backspace and actually get "back" on browser instead of delete your text. or even if your browser had any connection problem. I had problem when adding new steps. it can be very useful and relaxing to know that my work hasn't gone due to any problem.
20 votes -
Task Board - Add Option To Continue run for Test set
Currently you can select "Run" and start from scratch, but no way to continue from where you left off.
19 votes -
Add option to collapse/expand steps that calls steps from other test cases in test set&runs
Having the option to create a test case and call other test cases as steps is great feature. When you include that test in test set & run and start executing it then all steps from the called tests will be automatically displayed. This means if i called on my test , 4 other tests each with 10 steps , then my test will start with over 40 steps configuration. That makes the test heavy and all of that information might be useless for some people who can understand the whole test case only from the title. In order to…
14 votesThe idea of this function is to copy the steps as an integral part of the test. For what you are describing it may make more sense to create a test set that includes these tests and then you can choose to use the FAST RUN option in case you don’t want to go into the tests and execute the steps one by one.
-
13 votes
Batch edit is planned only for the grid views
-
adding test set to test set
Testset that contains several existing testsets
what do you think?11 votesHi,
Thank you for posting this feature request.
Kindly note that you can create filters in order to group multiple Test Sets together, find more information about Filters here (https://www.practitest.com/help/settings/custom-filters/)
Please let us know if you have any questions.
Best regards,
Christine -
Comment for test rejection
When test status is changed from "Draft" to "To Repair" or "Obsolete" a comment should be attached explaining for the reason.
11 votesA comment can be added but we don’t think we will add the option to make it mandatory at this point
-
clone a requirement
Please add a way to clone an existing requirement (to be modified later).
11 votes
- Don't see your idea?