613 results found
-
1 vote
-
1 vote
-
1 vote
-
1 vote
-
1 vote
-
1 vote
-
Translate in french
For your French clients, translate in French.
5 votes -
Link a TestSet to a filter on tests
I'd like a TestSet that updates itself automatically based on a filter I create in tests
Lets say I have in Tests, a filter
"V1.9" and add 20 tests
I then create a test set and link it to Tests/V1.9
20 tests are now in the test setI add 10 more tests to Tests/V1.9 and now I have all 30 tests in my test set
2 votes -
Inline edit fields after cloning a test (Test name & Description)
When I clone a test, the edit dialog is displayed
I always want to edit the test name and description(almost always)It's a (minor) irritation that I cannot just type in the fields directly, instead I must press the "Edit" button
1 vote -
I would like the ability to @mention someone in a text field
In Apps like Outlook and MS Teams, it is useful to "Mention" a user when I need their attention
Lets say I am writing a test and need help, in a step I could say @Nick Ambrose, please check my logic here
Then the user could get notified in-product or with an email that I need help (or their attention) and get a link to the item I need help with
1 vote -
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
- Don't see your idea?