39 results found
-
execution progress graph with costume fields
We would like to have execution progress graph displaying custom fields.
example:
a execution graph with ("automated", "planned for automation",...) fields.40 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 -
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 -
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 -
Synchronize PractiTest fields with JIRA fields (field mapping)
There are several fields in JIRA that we need to be reflected in PractiTest. In particular we use a fix in version field to associate releases in Jira and we need that field to be updated in the corresponding PractiTest ticket. Other fields such as priority should be mapped and synchronized.
We spend a copious amount of time with each release/sprint updating Requirements in PractiTest to reflect what the PMs have assigned for the current development cycle. Each time a requirement falls out of scope or a new on is added, we have to manually update PractiTest.
17 votes -
In The Task Board As Well As Filtering by Person why not filter by TestSet Filter & Test Filter -
That way you can multi purpose it for multiple test runs.
15 votes -
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 -
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 -
13 votes
-
Improve parameter handling
Sometimes we include the same test case a couple of times in one test set, but with different parameters. Unfortunately now we must edit those parameters one by one - and this is a lot of clicking.
I can see 2 solutions:
1) Allow modifying parameters directly in test set table
2) On parameters screen differentiate parameters by test case instance/number12 votes -
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
11 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 votes -
Ability to copy a filter
Have the ability to copy a filter within and across modules.
10 votes -
9 votes
-
9 votes
-
Add the ability to add custom fields and modify columns for Test Instances Run History
Right now, we only have:
- "Run date"
- "Status"
- "Tester"whenever we look at the test run history for instances. It'd be neat to have the option to add custom fields so we can better track previous runs.
For example: I want to be able to add "Commit hash" and "branch" to test instances run history so I can see the last GitHub commit that was tested.
7 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 -
Add batch operations to search results
It would be great to be able to perform batch operations to search results.
5 votes -
add the ability to use multi-lists as a child of a linked list
Currently, linked lists only support standard lists as the child item. There should be an option to add both lists types as the child of a linked list.
5 votes
- Don't see your idea?