603 results found
-
Add ability to get the steps based on filter-id.
I want to get the steps of test cases which are in Automation status (Automation filter).
3 votes -
Add a Check Box for Tests that are just Steps that are reoccuring but not needed in the TestSet
There are many cases where "Login as.." for instance is just called by other tests so that is not repeated in every Test, These "Login as" Tests are necessary but not necessary in the TestSets. Could a small check box, "Do not include in TestSet" be added so when we create a TestSet the Unnecessary tests are not visible or Color Coded to let the Tester know that Test is not needed in the TestSet? We are currently using xx as a prefix in the Test Name to distinguish these types of tests. Love your product!
3 votes -
Add Test Data field to Test Run similar to Preconditions for the Test
Similar to Preconditions in Test Run, add a field Test Data that shows up while running a test
3 votes -
Enable automatic download of reports
Currently get an automated email with a link to click to download the report. I would like the report downloaded automatically.
E.g. If I could anticipate the link to download the report (as currently added to the email) I could generate it automatically and hence download the report. You might also provide an api style interface such that the report is available in chrome as a page which can be extracted from chrome as JSON.
P.s. Not a good solution for me, but still a solution, have you thought about a google drive interface for the reports (and exports) to…
3 votes -
API v2: Deleting a run from an instance
Currently the API v2platform supports Delete method call for object such as Steps/Requirements/Tests/TestSets.
As part of our work in the company we post automated runs results to the run data of an instance and sometimes it accumulates a huge amount of runs in the history which slows down the retrieval of data via the Practitest platform.
so it would be nice if we could delete the runs from the history either bulk deletetion or by ID5 votes -
Email notification to cover the changes done at Step description and expected result level
Currently, test modification email notification does not inform the Test admin about the exact changes done at step description and step expected result. This is must needed request . Even Project history does not keep the record of test modification at the level of Steps description and Step expected result
3 votes -
Update the call on issue creation in YouTrack synchronization
PractiTest supports a synchronization with YouTrack, especially for the bug creation (from PractiTest to YouTrack).
There is currently no way to change the call on PractiTest test side.
YouTrack proposes a feature to update object on Event, such as issue creation.
I would need to identify that the issue is coming from PractiTest, and then I would be able to make my change on YouTrack side.The signature includes 2 fields, which are not filled today: externalId and externalUrl, which shall be filled in my opinion when the issue is created from an external tool.
Could you please fill at…
3 votes -
We would love the ability to run cURL commands form within Practitest so that we can launch our automation from within a test run.
We would love the ability to run cURL commands form within Practitest so that we can launch our automation from within a test run.
3 votes -
Create Pie Chart with group of values
I would be interested by having a way to group different values of a field used to create a pie chart in 1 "super value"
To give an example:
For the Requirement items, I would like to have a pie with only 2 values :
- Not Covered
- Covered
As of today, we have: Not Covered, No Run, Passed, Failed...
I would like to be able to present a dashboard to my manager with the value "Covered" including all the values except Not Covered and Not Covered.3 votes -
Only display step information that failed when creating a bug using JIRA integration , do not include all steps
When creating a bug using JIRA integration currently all steps in the test are pased into the jira description. It would make more sense to only paste the step that failed and the results from that step. this would give the user the information on the actual issue and reduce the amount of editing currently required using jira integration
3 votes -
3 votes
-
Multiple selection on requirements
When you select the traceability of a requirement you can only add one test at a time, can we have a multiple selection like the add instances on a test run?
3 votes
Ido Tandy
responded
-
Should increase Pie Charts capacity in the same tab
We use a tab for each version and there, we have a pie chart for each build from that version.
At this moment, only 8 pie charts can be created in a tab.We would like to be able to add more Pie Charts, for better visibility of all builds from that version.
Currently, we can either delete old build pie charts or create a second tab for the same version, both which are not good solutions. After each version, we send a report with all builds from that version and a guest link for stakeholders to see the progress,…
3 votes -
Add the ability to sort the rows and columns in the tables on the dashboard.
Add the ability to sort the rows and columns in the tables on the dashboard.
This would enable the column order in the issues table to follow the lifecycle. i.e. New - assigned - fixed - closed etc.3 votes -
Create trending chart for custom fields of instances
Create trending chart for custom fields of instances
3 votes -
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 -
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 -
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 -
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 -
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
- Don't see your idea?