613 results found
-
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 -
Can you please revert the UI back to an old view? Or reduce blue colors. My eyes are burning after couple hours of staring at it.
Can you please revert the UI back to an old view? Or reduce blue colors. My eyes are burning after couple hours of staring at it.
1 vote -
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 -
3 votes
-
Linked Requirements in Requirements Traceability
Expand traceability in Requiremnets to include Linked Requirements., This will enable association between Business Requirements to Functional Requirements etc.
Also supports a heirachy of requirements (drill down).
It appears that the change would be relatively simple given the existing Traceability functions in Requirements for Linked Tests and Linked Issues. Just add Linked Requirements.
4 votes -
Create multiple task boards in one project
I want to have the ability to create dedicated Task Board tabs - just like we have dashboards now.
1 vote -
Mapping Jira issue type with Practitest field
When we sync Jira issue to Practitest - whether it's going to be an issue, or a requirement - we can only see which type it is in Jira in Description field.
If we could map it to custom field in Practitest, it will help us organizing them in Practitest per issue types, for example, with Filters.For example, we sync both Stories and Epics as Requirements, I want to build a filter (autofilter for example) which shows which Requirements are Stories and which are Epics.
6 votes -
keyword search loses many test cases
When I enter a keyword and search, many test cases with the keyword will not show.
Now just crtl+F for every page and it is miserable...9 votes -
Linked lists in filters
I have two suggestions about the use of Linked Lists in filters:
Suggestion 1. If I use a parent list in the criterion, the criterion of a linked list should show me only the values that are related to the parent list value.
For example, I have two fields
Feature - values A, B
Sub Feature - values (A) 1,2 ; (B) 3,4
If my first criterion is "Feature is A", and I start to create criteria "Sub Feature is..", then the dropdown list should show me only values 1,2. Currently it shows 1,2,3,4Suggestion 2: If I use the…
21 votes -
Add to API test creation: field 'Test Preconditions'
I worked with Robot Framework and create a plugin for report tests into PractiTest
For the robot, precondition flow is an important part of the test, so such an option makes PractiTEst tests created from the robot more sense fully2 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 -
1 vote
-
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 -
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 -
Allow to sort list field values in descending order
Currently, there is an option only to sort them in ascending order. If you need to sort them in reverse order, you can only do it manually
4 votes -
When cloning a new project, add an option to clone filters
Right now when you try to clone a project from Account settings, you have 4 options:
clone fields, clone users, clone user groups, clone integration settings.It would be also very useful to clone filters. Probably should be related to "clone fields" option
8 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 -
Adding more fields to panel with PractiTest data in Jira ticket
I'd like to see more columns displayed in JIRA when the linked Tests from PractiTest are displayed - or Steps of a run if it's a bug.
For example, for linked Tests:
- Assigned to
- Tester (of a last run)
For bugs
- Priority (if it's different in PractiTest)13 votes -
Sending attachments via Firecracker
Ability to send attachments - such as screenshots, or logs files - from the automated test runs via FireCracker
3 votes -
Hide PractiTest button on tickets in Jira for projects not linked to PractiTest
Our company uses a variety of different Jira projects for everything from idea generation to corporate planning, in addition to software development. On Jira tickets unrelated to software dev, you can still see the "PractiTest" button, even though we have not integrated that project to PractiTest.
It would be great if this button was only displayed once the link was established in both Jira and PractiTest, so that our leadership team that's using Jira for other purposes doesn't get confused by it.
1 vote
- Don't see your idea?