562 results found
-
Create trending chart for custom fields of instances
Create trending chart for custom fields of instances
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 -
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 -
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 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 -
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 -
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 -
3 votes
-
modified test differentiated & Lock "update the original test"
if a test in a test instance is modified, it would have been marked somehow so it would be differentiated from the original test.
In addition that an option to lock "update the original test", so he won't be able to easily update the original test.
Give an option to change a test for a test set for all runs, in a way that it doesn't "call" the test but clones it while giving an option to edit it.
3 votes -
zenhub
2 way integration into zenhub.
3 votes -
Grouping of Dashboards
We have made some dashboards for our progress, one that shows all sprints, and one for each sprint. That means that there will be many dashboards, so a possibility to group dashboards would be nice. So that we could have just “All Sprints” as a tab, but a hover on the tab shows a menu for each of the Sprint dashboards.
3 votes -
Allow for creation of conditional test steps
For example:
Step 5: "Select the folder with today's date"
- Condition: If folder does not exist, follow these steps (link to other steps, or insert in situ).
If the folder does exist, have the ability to skip the does not exist condition.
Sort of like an if-then-else statement inside a Test Case3 votes -
Controlling "Notification List" with PractiTest API
In PractiTest API, "Notification List" of "Issuse" cannot be read and set.
Please take action to expand the scope of use of the PractiTest API.3 votes -
Test Library Filter - show number of test instances in View
When creating / editing a Test Library Filter, in the Custom Field area, I'd like to have Instance Count shown in the Filter View.
3 votes -
Tables, Font sizes, inline attachments in Test cases description and test steps.
The following issues/suggestions related to description and test steps of a testcase(test library, requirement & test set/test execution):
1) In my organization we use JIRA and most of the stories contain data in tables with many rows and columns . When testcase( &requirement) is created from JIRA into PractiTest, data in table is displayed in between || in PractiTest. When the EYE icon in PractiTest, Table is not displayed. It will be great if we can at least display the data in table format when EYE icon is displayed.
2) When we contacted Joel on the help chat, he showed…
3 votes -
Can we specify Test Results file with xBot script run?
We have a field "Results Path" under Automation info tab while adding an xBot Test Case from PractiTest. Can we have a field to specify the Result file to upload during script run?
3 votes -
Allow the ability to search for a specific Test:ID number in the Search available in the Top Main Menu Bar.
If you have a large number of tests in your Library and you are wanting to edit or revise a specific Test ID, it would be more efficient to allow the searching for the Test:ID rather than having to note details from the title of the test and search against that...easier and quicker to remember a number...
3 votes
- Don't see your idea?