603 results found
-
Grouping of Dashboards
We have made some dashboards for our progress, one that shows all sprints, and one for each sprint. That means that there will be many dashboards, so a possibility to group dashboards would be nice. So that we could have just “All Sprints” as a tab, but a hover on the tab shows a menu for each of the Sprint dashboards.
3 votes -
Don't scroll to the top of the page when clicking the menu icon for a filter
When a filter name is low on the page and you click on the menu icon next to it, it scrolls you to the top, causing you to have to scroll back down the page to the filter.
4 votes -
Add tables support
add an option to create, and modify a table in a test's description, expected results and actual results.
and also to paste a table directly to any of these fields.
6 votes -
4 votes
-
Enable sorting on the columns in the pop-up to add test cases to test sets
When adding test cases to test sets, the pop-up you have to select them in has no option to sort the listed test cases - which makes us very dependent on detailed filters or the list becomes hard to work with for us with +10 sub-pages to click between to find the right test case.
We suggest to enable sorting on the columns, so we can sort by name or ID.1 vote
Ido Tandy
responded
-
If step name is blank, add the step number in the history tab
Right now it will just write "Updated step " and you cannot know what step was updated, were if you have step names it will write "Updated step [step name]"
We find it time consuming to always name steps, and step name and step description are often duplicates, so we would like to have the option to not user step names, but still get the history when steps are changed1 vote -
1 vote
-
Step parameter in preconditions field
We would like to have step parameters in the preconditions field as well.
5 votes -
Trigger reminders to ensure test coherence between results and issues
Currently, I am using an extraction of issues and test statues to identify in Excel:
- Failed tests linked to closed issues => for testers to update the status of the test
- Failed tests not linked to any issue => for testers to link them to an issue
- Highlight the issues that need to be replied to or retested (e.g. rejected, fixed)This involves:
- Duplicating lines where tests are linked to several issues
- Vlookups between issue statues and test statusesMy idea would be to have triggers in the UI and perhaps also by email to…
1 vote -
zenhub
2 way integration into zenhub.
3 votes -
modified test differentiated & Lock "update the original test"
if a test in a test instance is modified, it would have been marked somehow so it would be differentiated from the original test.
In addition that an option to lock "update the original test", so he won't be able to easily update the original test.
Give an option to change a test for a test set for all runs, in a way that it doesn't "call" the test but clones it while giving an option to edit it.
3 votes -
3 votes
-
Instances : Assigned for filter to be made available
Allow users to create a filter in the Test Sets & Runs module that will only show test sets with instances assigned to them.
This way if a tester has been assigned multiple test instances across different test sets, he can see all of them at one shot instead of going through each test set to find what's allocated to him.
3 votes -
Make step name not required when importing from spreadsheets
Step names are not required within the tool and it is an extra hassle to have to include them when we import test cases from a spreadsheet. Could you make that a non-required field when importing?
1 vote -
Support Issue updating provision of batch API
in the big project and data increasing, we noticed the API call limits stops developing and integrating with automation testing pipleline.
It would be a great to run testing and updating issues if PractiTest support provision of batch API to avoiding limitation of API call (100 / 1 mins, and returned records )
9 votes -
Add issue fields to tabular report
In the tabular with steps report it is not possible to configure which fields to add to the issues tab, for example, priority.
1 vote -
Add a way to Batch Edit Tests. Now you have to go into each test to change a name
Add a way to select a bunch of tests then batch edit them to make a single change to a bunch of tests. That way, you don't have to go into 1 (of say 1000) tests just to modify the test with ONE word. So, if my tests name is Batch Production Phone Edit and I want to change it to Batch Production Phone Edit 1, Then Batch Production Phone Edit 2 etc. etc. I can just select each test and then batch edit to add the numbers to the end of the test title.
3 votes -
Column customization in test sets
I have a requirement to enable adding tests directly in test sets. Presently, when we try to add a test instance there, it shows just 2 columns. Test ID and Title. There is no way I can add more columns and resize the window.
That's required when we want to create different test sets as per execution type, test level or as per area/application field(custom fields).
Only way to do that now is create different filters as per the need in test library, get the tests and add them to the instances.
Since in my one project, I have 5-6…1 vote -
add the ability to rename a cloned test or test set at the time of cloning
This way we would not have to go back and edit the name of the test or the test set later.
1 vote -
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
- Don't see your idea?