39 results found
-
Open issues per test set
Create a new tab (next to History) in the test set that shows a list of open issues linked to test instances in the test set.
The linked issues column is not useful when there are a large number of instances and the bold/faded text for the issue number is confusing.
A simple list of issues that can be sorted by priority lets me know what needs addressing and I can go into each bug.3 votes -
Including the "Expected Result" for all steps in the description of a new issue created via "Fail & Issue."
Currently, the auto-generated description for a new issue created via "Fail & Issue" includes only the Expected Result for the failed step. We would like it to include the Expected Results for all steps leading up to the failure as well.
1 vote -
Add the ability to recognize duplicate test cases
As a user, I want to know if my library contains duplicate test cases
1 vote -
1 vote
-
2 votes
-
Add ability to show data in percentages in distribution tables
As a user I want to be able to see data in percentages in distribution tables in the dashboard
0 votes -
Add the ability to filter out run statuses for execution progress graph
When creating a new execution progress graph, I want to have the ability to decide which run statuses the graph will show to exclude irrelevant statuses
0 votes -
Add the ability to select absolute dates for execution progress graph
In addition to relative dates, add the ability to select absolute dates when defining an execution progress graph
0 votes -
Why put a toggle Preview button if it does not match the format after saving
When creating test cases, we usually use nested lists. Considering many limitations on that text area field in terms of format, I rely on the toggle preview to see how it will look like once I ran the test case. However, that is not the case. Can you please fix the formatting on lists there are like a hundred issues on that module alone. Then after that, make sure the Toggle Preview does its job.
3 votes -
Add the ability to create a not cumulative progress graph
This graph should show the daily progress rather than cumulative progress
0 votes -
Export Project history
It would be nice to have an option to export Project History as an excel file, according to the filtered results.
3 votes -
Need the ability to Create/Read/Update/Delete filters through the API
Need the ability to Create/Read/Update/Delete filters through the API
6 votes -
The ability to create a filter tree from a single screen rather than having to create individual filters and link them together
The ability to create a filter tree from a single screen rather than having to create individual filters and link them together
6 votes -
Clone a step in a Test edition
Add the possibility to simply clone a step. for instance a 'clone step below' option that would copy/paste the test step fields and allows to edit them
1 vote -
Firecracker integration | add fields to configuration by XML properties and not only attributes
The idea is to be able to add custom modifications to the practitest configuration when using firecracker by using the XML properties in addition to current option by using XML attributes
13 votes -
9 votes
-
Improvements to Exploratory testing
When using Exploratory testing can we have an option to:
(1) Take screen shot and add comments via the tool itself
(2) record all the screen actions as a recording.
(3) Convert all the actions automatically as steps if you want to make the test a scripted one for later use26 votes -
Give users the ability to add custom fields at Test Step Level.
You should give the users to add fields at test step level.
They should be allowed to Add things like Test Data for a particular step like Large Queries it it. For us the Test Precondition or Test Description or Test Name cannot be used for that purpose.
13 votes -
Add requirement link to an issue when posted to Jira
When an issue is created from a test, the associated requirements could be linked (if Jira requirements, then the Jira requirement link) to the issue document (perhaps appended to description, or to a field defined in Practitest by the user) before being sent to Jira.
Why? So in Jira a developer can click straight on the requirement to see what should happen, rather than dig through a number of screens to access the requirement26 votes -
make requirements links visible when executing a test
When executing a test case one of the key things you'll want to reference are the requirements, so logically they should be accessible.
33 votes
- Don't see your idea?