564 results found
-
3 votes
-
Instances : Assigned for filter to be made available
Allow users to create a filter in the Test Sets & Runs module that will only show test sets with instances assigned to them.
This way if a tester has been assigned multiple test instances across different test sets, he can see all of them at one shot instead of going through each test set to find what's allocated to him.
3 votes -
Make step name not required when importing from spreadsheets
Step names are not required within the tool and it is an extra hassle to have to include them when we import test cases from a spreadsheet. Could you make that a non-required field when importing?
1 vote -
Support Issue updating provision of batch API
in the big project and data increasing, we noticed the API call limits stops developing and integrating with automation testing pipleline.
It would be a great to run testing and updating issues if PractiTest support provision of batch API to avoiding limitation of API call (100 / 1 mins, and returned records )
9 votes -
Add issue fields to tabular report
In the tabular with steps report it is not possible to configure which fields to add to the issues tab, for example, priority.
1 vote -
Add a way to Batch Edit Tests. Now you have to go into each test to change a name
Add a way to select a bunch of tests then batch edit them to make a single change to a bunch of tests. That way, you don't have to go into 1 (of say 1000) tests just to modify the test with ONE word. So, if my tests name is Batch Production Phone Edit and I want to change it to Batch Production Phone Edit 1, Then Batch Production Phone Edit 2 etc. etc. I can just select each test and then batch edit to add the numbers to the end of the test title.
3 votes -
Column customization in test sets
I have a requirement to enable adding tests directly in test sets. Presently, when we try to add a test instance there, it shows just 2 columns. Test ID and Title. There is no way I can add more columns and resize the window.
That's required when we want to create different test sets as per execution type, test level or as per area/application field(custom fields).
Only way to do that now is create different filters as per the need in test library, get the tests and add them to the instances.
Since in my one project, I have 5-6…1 vote -
add the ability to rename a cloned test or test set at the time of cloning
This way we would not have to go back and edit the name of the test or the test set later.
1 vote -
1 vote
-
include the ability to add tests all at once instead of individually when adding tests on the traceability tab in requirements.
We often add 10 or more test cases to each requirement which means having to click "Add" that number of times to link each test case. It would be nice if there was a way to add all of them at once.
1 vote -
Should be able to download attachments per test
For auditing purposes would be nice to be able to download the screen shots or attachments for each test.
This way i can send to the auditors during audit season
3 votes -
Allow showing more than 5 updates on "Latest updates" for dashboards
Currently the latest updates chart for dashboards only shows the last 5 items. Being able to show more than just the 5 latest updates would be useful to provide a better insight into what is being worked on inside dashboards.
Adding a way for users to select an amount of updates to show would be a good solution, allowing people that only want to see 5 updates to still only see 5 but allowing others to see more if they wish to.
1 vote -
1 vote
-
Add new value to standard or custom fields via API
In a context of automated test, it could be valuable to be able to append new values to fields already existent via API.
At the moment, we can only replace the entire Field with new possible values. And if something goes wrong, I feel like there's a high chance to lose information.
17 votes -
9 votes
-
Step parameters to be made available for a test instance
It shall be possible for us to see what step parameters have been used to run a test instance.
Test instance grid only shows the last param value with which that test instance was run.
Inside a test, we have multiple test instances, having information at one place makes it easy for us to review that team has covered all the possible test data1 vote -
Allow either cloning or sharing custom fields to step parameters
Mostly custom fields would be used as step parameters. It would be great if we can allow cloning or sharing or copying custom fields to step parameters
3 votes -
Allow to customize a HEADER for the exported PDFs, so they can be usd as Controlled Documents
This should include:
1. Company Logo
2. Document title
3. Date of issue
4. Document ID number and Revision
5. Number of pages (current page / Total number of pages)1 vote -
Allow access to Test Step Actual Result data via the Practitest API
Allow access to Test Step Actual Result data via the Practitest API
We would like to create a bespoke report using our existing report server. To do this we need to extract all of the Test Result data via the API. We are using the API so that we can automate the process.
[1] At the moment you are unable to access the Test Step Actual Results via the API.
[2] At the moment you are unable to access the Test Run or Test Step attachments via the API
This make building a comprehensive bespoke report difficult. Would it be…
2 votes -
Custom Field - Edit Value - Linked List type
Custom Fields Customization missing edit value name (Linked List)
This can be done for Link type but not for Linked List
1 vote
- Don't see your idea?