544 results found
-
Mantis 2-way integration
For now Mantis is a 1-way integration. Which means that once a test failed, the bug is created in Mantis.
The problems are :
1- we have to manually re-link the bug in Practitest
2- No info appear in the Report unless we re-recreate the bug in the Issue part.Having these 2 features would be a great improvement.
Thanks !1 vote -
Allow creating a test set based on requirements
Allow creating a test set based on the tests linked to one or more requirements. Example:
- search for all requirements with tag 'ABC'
- select all or some of the requirements
- click the 'Create Test Set' button/link above the resultsAll the tests linked to each checked requirement is put into the test set.
5 votes -
9 votes
-
Have an option to include/add test cases that aren't already part of test set.
Currently, when you want to add a test case that doesn't already exist in a test set, user has to scroll through pages to find the test case. Marking the test in red doesnt really help
It would be great to add an option to filter out test cases that are not part of the test set and add them.
4 votes -
Attach files on bug report
To be possible to attach files at the time the bug is reported to Jira.
1 vote -
1 vote
-
1 vote
-
1 vote
-
1 vote
-
1 vote
-
1 vote
-
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 -
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
- Don't see your idea?