603 results found
-
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 votesIdo Tandy responded -
2 votes
-
Add the ability to convert an issue to a test case
If we determine that a bug is a good test case, It would be great if we could convert that issue to a test case from the issue detailed page.
Add the ability to convert an issue to a test case so the user doesn't manually have to add a new test case.1 vote -
Adding a testset id field which can be used to filter issue reported for a particular testset and see them on dashboard
Please have a feature which enables a user to see the dashboard updated with the number of defects raised for a particular Testset. Right now it is doable through the reports. But since Dashboard is the landing page of Practitest, it will be better if we can have that feature on dashboard also. May be we can have a field for test set id which we can add it in the Issue filter to update the dashboard view.
1 vote -
Provide Notes section at filter level for documentation
We use filters to separate our application by functional area. Some functional areas have specific setup and test instructions. Currently we have to list those instructions in each test or link to confluence. It would be helpful to have a Notes section at the filter level that would allow you to store text to list specific instructions , set up, etc.
3 votes -
Implement a step library, and/or allow "call to test" subsets
We have many steps that are reused all over the place, but not necessarily in the same order. We also have step sequences that, on their own, do not constitute complete tests. So we now have tests that exist only as step sources for other tests, sometimes with a single step each.
It would make more sense, as a user, to have a library of individual steps and step sequences that can be referenced without having to create tests just for this purpose.
Another way to do this would be to allow "call to test", or something like it, to…4 votes -
Make the "Add requirements..." field case insensitive
In the test Traceability tab, the requirements field ("Add Requirements by typing their ID's") is case sensitive. This is annoying, especially since the failure does not say anything about capitalization. All requirements are upper case, so capitalization can be assumed.
1 vote -
Have an option to define multiple type for a 'Filter'
Currently we can define only one type for a filter, so we have to create same filter for different types. It will be great if we can choose multiple type for a filter.
3 votes -
Make charter not a mandatory field for exploratory tests
"Name" and "Charter" in some cases can mean the same thing and in that case where it does mean the same thing Charter should not be a required field.
2 votes -
Add the ability to auto-reopen a closed bug when it is linked to a failed test step on a particular test run
Add the ability to auto-reopen a closed bug when it is linked to a failed test step on a particular test run
7 votes -
Integration with Katalon Studio
I am exploring the open source Automation tool Katalon Studio for automating test cases for mobile and web applications. I would greatly appreciate if Practitest can provide 2 way integration with this tool.
11 votesIdo Tandy responded -
8 votesIdo Tandy responded
-
Move Cloned reference to History section
When Cloning a test, the cloned test has a reference of the test from it was cloned and it shows up in the "Attachments" section of General section. It would be nice if this reference could be moved to History section to keep the test look cleaner
2 votes -
Add the ability to add folders/filters from Test Library to Task board
Generally testers write multiple test cases for a user story or feature and generally we group them in folders/filters in Test Library module. The ability to add the folder/filter to task board would be a better idea to track it in the board
3 votes -
Make it possible to change the 'test set' on a run test instance
Add the ability to change the 'test set' that an instance of a test is in, once it has been run
We have some test instances which have been added & run in the wrong test set. We want to move the run instance to a different test set, , for reporting purposes., but not loose the results and run history10 votes -
Add an ability for optional steps
Would be nice to be able to set steps within a test to "optional".
1 vote -
Integration with TestComplete and XamarinUI Test
Integration for Automation tools for Desktop and mobile applications
1 vote -
Give permissions for individual fields to certain users
I want to be able to give certain team members permission to edit picklists on only some fields ? eg) we have a custom field 'Run on Build' that we want all team members to be able to add values to, but don't want them to be able to have general access to edit values of all other fields
10 votesIdo Tandy responded -
Allow users to rename Transition Status.
Renaming Transition Status will save us some time in case we misspelled a status, but don't realize it until we are done completing the transition workflow.
1 vote -
Add step numbers on to Step when re ordering
When clicking on Reorder Steps for a Test - the steps appear as a long list without the Step Number next to them. This makes it hard for the User to know which Step to swap around. Please could we add the Step Number to the title of the Step.
12 votesThe reordering feature will be enhanced in the new Test Form, allowing you to easily reorder items within the Steps tab using drag-and-drop functionality. We're actively working on this, and it will be released in the coming months.
- Don't see your idea?