110 results found
-
0 votes
-
0 votes
-
0 votes
-
0 votes
-
User groups with permissions lower than Commenters should also be free from billing
We moved to the new pricing, and found that it works differently from the old one:
In an old one, if we create a user group with permissions lower than those of Developer, each user in such group was still billed for $9.
New pricing has a user group Commenters, and we're not billed for the users we add to this group. However, if we create a user group with LESS permissions than commenters - for example, without viewing permissions on certain module - we're billed for this as a Tester.I think this part of billing should worked as…
1 vote -
Drag and drop option for the filter
For example, if I'd like one Filter to get out of the Parent filter. Or, on the contrary, to put a Filter under another one.
I know I can edit its setting, but it can be also nice if we could have such option in the view page itself - to drag and drop a filter to another place in hierarchy4 votes -
Add "+" and "-" for edited test case in history log
It would be better to see the changes in the test case history log when the test was updated by adding "+" (for addition) and "-" (for removal) signs in front of each change
27 votes -
Running Postman call from Practitest
Similar to Xbot triggering scripts from local machine, I'd like to either trigger Postman API Call/Request, or the whole collection via Practitest.
3 votes -
option for cloning traceability (linking between requirements and tests)
Whenever I need to clone Tests or Requirements I have to do double work of adding back linking between entities an option for cloning not only attachments but also linking between Requirements and Tests would help.
26 votes -
Allow to select from used tags when entering Tag as filter criteria
When creating filters and tag is selected as filter criteria - choose from list of used tags (select with search) to avoid spelling mistakes
39 votesThis request is not in our current roadmap.
-
Link test to test
Please make it possible to link test cases between each other
40 votesWe have not found a justification for this request.
-
Create the ability to import parameters
Rather than having to copy and paste parameters in from a datasheet, it would be good if we could map the parameters for multiple instances of a test case to a datasheet and import them
eg Select 10 instances of a test case, click an 'bulk update parameter' button or similar, which can then map to an excel datasheet22 votes -
Add API to upload .trx files
standard .net test runners can produce .trx files e.g.
vstest.console.exe /logger:trx foo.dll
dotnet vstest --logger:trx foo.dll
These are just XML files. We currently have to parse these xml files and perform hundreds of individual uploads, waiting 60 seconds every time the server throttles with HTTP 429
It would be better if .trx files could just be uploaded to practitest to produce a run of a test set, and the parsing was done on the server.
13 votes -
9 votes
-
Task Board - Add Option To Continue run for Test set
Currently you can select "Run" and start from scratch, but no way to continue from where you left off.
19 votes -
Translate in french
For your French clients, translate in French.
8 votes -
clone a requirement
Please add a way to clone an existing requirement (to be modified later).
11 votes -
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 votes -
8 votes
-
Generating Test Cases From Jira into Requirements
The ability to go into the 'Requirements' section in PractiTest and have an option to 'Generate From Jira'. This would grab an attachment (Excel, CSV etc) from the Jira ticket, import it into PractiTest, generate a test case from it and link it to the requirement
13 votes
- Don't see your idea?