603 results found
-
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 -
Report Cloning needs to be better and more functional
this is about the clone report feature not being helpful. I need to make exact same reports for different filters. I try to clone but the cloning report feature is not helpful at all. I need to select the displayed fields in the report every time, even if I clone it. Ideally, cloning should automatically clone the list of display fields that I have chosen in my source report but it doesn't happen.
3 votes -
Upload attachments directly to Jira issues created from PractiTest
It would be nice to have the option to directly add attachments when creating an issue using the Jira integration.
In our case issues created require a certain backup to be attached, right now testers always have to open the created issue in Jira afterwards to add this. This would be made easier if attachments could be uploaded directly when creating an issue from PractiTest.
Possibly even uploading attachments from the test run as well to provide some more background information / possible ease of use.
3 votes -
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 -
Implement Full Traceability - If Req linked to Test Case & Issue linked to Test Case, then system should show Req & Issues linked,
Implement Automatic Full Traceability - If I have a Req linked to a Test Case & I create an Issue that is linked to a Test Case, then the system should automatically link and show the Req & Issue linked. I should not have to manually link them.
3 votes -
Import via Excel should have an update option as well not only to create new
Currently export a Test or Requirement -- creates new records. User should be able to update via excel for the records that is already existing using Entity ID
11 votes -
Add option to auto fill actual results with custom text
The past two QA jobs I've had required us to fill in our actual results even if they matched the expected results. Currently they want us to fill it in with something simple to show that we acknowledged it passing as expected, for regulatory purposes.
Could we get some type of configuration for this so that if we pass or pass all and leave the fields blank they will be filled in with custom text (e.g.: "Passed as expected")?
4 votes -
Copy and paste parameters across Test Instances
It would be very time saving being able to copy and paste step parameters across Test Instances in a TestSet.
The current workaround is to write the parameters somewhere else, then bulk edit the Test Instances with the parameters to be pasted.Even better, a spreadsheet-like editor would solve this issue: one row per Test Instance, one column per parameter.
3 votes -
Search also across Test Instances
Extend "Search" scope to all Test Instances, including the expected and actual results.
It would be useful to locate a specific instance that fails with a specific value/output.3 votes -
Make it possible to create requirements in PractiTest and have them carry over to Jira
It would be nice if you could create a requirement in PractiTest and have it display as a story / task / subtask in Jira. It's possible to bring in requirements from Jira into PractiTest but not the other way around.
3 votes -
PractiTest Test Management for Jira Add-on usage
We need to determine add-on usage in our instance. We are sure this add-on is in use; however, we are unsure where. Can you please provide the best method to determine where or if it is being used?
Thank you!
1 vote
- Don't see your idea?