560 results found
-
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 -
Add the arrow navigation controls for pages of Test Instances under Test Sets and Run to the bottom of the lists of Test Instances
Add the navigation controls for pages of Test Instance under Test Sets and Run to the bottom of the lists of Test Instances...I am referring to the forward, backward, beginning of file and end of file arrows (that are almost missed being so small) which are next to the drop down for number of Test Instances shown on a page. It is frustrating to scroll to the bottom of a 100 Test Instance list and need to go to the next page only to have to scroll back to the top to access the controls to go to the next…
3 votes -
Add the functionality for the list of pages to maintain the history of which page the user is currently on.
When you are in a specific Test Case, which happens to be on a page which is not the beginning page (Page 1), and you back out of that Test Case, it is very frustrating to be sent back to the very front of the list of pages instead of backing out to the page of Test Cases you were on before selecting one to view. Example: If you are on page 4 in a list of 1000 Test Cases (display 100 Test Cases per page set) and had been looking at one particular Test Case and then back out,…
3 votes -
Allow updates to test cases via the API to function as expected.
Currently, if you attempt to update a test case that is currently in the test library, there are some fields that will not update. For example, if one attempts to update the folllowing fields:
"automated-test-info": {
"automated-test-design": "updatedDataHere"
}The API call returns a success, even though that data was never updated.
3 votes -
Remove the need to save in order to add attachments
Remove the need to save in order to add attachments: "To add attachments to this step you need to save your test first."
3 votes -
Add an import feature that imports the name and description of an external bug tracking issue
Currently we have to manually import the issue name and description and then Sync requirements and bug tracking issue.
A function that creates a new TestSet with the name and description fields imported from YouTrack or another bug tracker and then automatically linked to the Requirement would be great for productivity and streamlining!3 votes -
Add a link to the test via Test:ID
I'm missing the reference from Test Set to Test.
To see previous results of this Test, I have to go to the Test Library. A direct link would be more practical.
In the Test Instances list, there is a column Test:ID. When I go to the ID I want to jump to the Traceability tab of the Test.3 votes -
Can import requirements without applying mandatory fields
If I have a required custom field for a requirement that field is still blank when I import the requirement. I'd expect it to force me to select/enter a value, if it is required.
PractiTest vendor suggested to raise here:
Hello Narasimha,
Following my conversation with the Product Team.
The request to add a verification/error step in case of the Import Jira issue to Requirement is not a request for just an enhancement, but rather a request to change the current functionality.
If implemented, this change might affect many other customers, which do use the Jira integration with Mandatory fields…3 votes -
Sending attachments via Firecracker
Ability to send attachments - such as screenshots, or logs files - from the automated test runs via FireCracker
3 votes -
Integration of Run status of Practitest to Jira. We can integrate Run status with % from test set also.
Integration of Run status of Practitest to Jira. We can integrate Run status with % from test set also.
3 votes -
Stop Autosave from interrupting text input in Test Results
When typing detail in an annotation for a Test Result, the regular autosave interrupts text input so often characters that are typed are not entered. Can the autosave in place here and elsewhere be done without interruting input?
3 votes -
Have API key "Retry-After" give you the amount of seconds required before retry
The current response given for too many requests is :
{"errors":[{"status":429,"title":"Exceeded API rate limit of 30 per 60 seconds","Retry-After":"60 seconds"}]}
what would be useful if the key "Retry-After" gave you the amount of seconds required before retry and was just a number not a string. It appears it just gives you 60 seconds regardless of how long you've been in API jail.
either that or add a new key entirely for this purpose (probably would make change control easier to add a new key)
currently when im looping and uploading im having to work this out myself. Though i'm having…
3 votes -
Need test set same as sheet to execution. we want to save time and pract is too much process.
people use sheet why?
fast
easy to modify
give concise view
easy to update.test set with permutation and combination should be in same way as google sheet.
main test as column and test data as row heading
3 votes -
3 votes
-
Enhance project cloning function
We have more than 40 projects in our account and it's quite cumbersome to choose the project I need to clone from the list of projects without any order.
Either:
- add an option to start typing a project name and it will appear;
- sort the project alphabetically.Please!
3 votes -
View only Reports permission should be added
I have team members who should have access to reports and can download/re-generate them at any time, but I do not want them to change anything.
Currently, the permission checkbox for reports in the user group says: "View, Create, Edit and Delete Reports".I think there should be 2 checkboxes:
One just says "View Reports"
Another says "View, Create, Edit and Delete Reports"3 votes -
Differentiate between tests and tests with failures that are due to existing issues versus newly identified issues
At a glance it's difficult for devs, PMs, or other users not in Practitest itself but using Jira integration to tell if a test case has failed because of something new to the ticket, or something already in the system. Some mark or color differentiation would be valuable in sorting the two.
3 votes -
Ability to include PT fields as well as Jira fields in the bug raise screen
To help improve the filtering within PractiTest there are some fields that we want to only capture in PT. To help with this we want to ability to include both Jira and PT fields on the bug raise screen. Currently we need to go manually update the fields once the bug has been raised.
3 votes -
3 votes
- Don't see your idea?