614 results found
-
Select multiple values in setting filter from Multi-list field
When you prepare data in Multilist, there should be easier option to select them in filter preparation.
Actual:
Set up multi-list field (eg. task number for functions) and prepare TCs with these numbers.
Prepare filter with multiple values - you have separately prepare filter or you have to click "Or", "open dropdown", "select value" repeatly.Expected:
Use shift/ctrl to select multiple values from multilist.
There should be displayed filed with selected list.
Clicking on field opens dropdown with selected values for editation of multiselection.
"X" will be over whole multiselection and delete whole selection1 vote -
Ability to link a requirement to another requirement
Ability to link a BR to the FRs that supports the BR.
1 vote -
Add the ability to the boutton «Click here to create a new Requirement / test»
Add the ability to «Click here to create a new Requirement / test»:
It's possible to create a new Requirement or test with the relevant value in the fields automatically if we create it from the boutton «Click here to create a new Requirement / test». And it's possible to always keep the button «Click here to create a new Requirement / test» at the top of each filter page ?9 votes -
Add filters to Dashboard so user can create dashboards based on their queries or filters
Like I want quarter wise data or team-wise data I have to create a report for that instead of that if you can give that functionality in the dashboard that will be very helpful.
4 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 -
9 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 -
1 vote
-
Add project name column to Slack integration
As a company with many related projects that are reported to the same channel, we have a need for distinguishing between the tests belonging to different projects
1 vote -
Add status 'SKIP' for skipped test case while run an instance
Hi Admin,
while running of an instance, it had better provide a status 'SKIP‘ so that we can know how many test cases 'SKIP' in regression testing.
1 vote -
Adding a Header on External Dashboard
Similar to JIRA headers.
Ex: A dynamic todays date added to current release.1 vote -
Support to create / modify dashboard via API
Hi, While we integrated API into our testing pipeline, noticed that it could not create / modify dashboard via API.
Suggest to support this feature.
1 vote -
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 -
Ability to create a burn up report.
If we know of a particular release date and we want to track test execution to that date, then a burn up report can help us track and highlight risks at a very early stage.
This should take into account the testers available for the execution so that it can work out the velocity accordingly1 vote -
Please provide option to link Test set with Requirement.
Please provide option to link a Test Set with a requirement. As of now we have to link one by one all the test cases for a requirement and its time consuming when we have big projects with 300+ test cases.
70 votes -
Support Test Set configuration with JIRA integration
As a user, I need the ability to link the Test Set ID from PractiTest to the Story/Bug etc.with JIRA projects. Currently, the PraciTest - JIRA integration only supports the configuration to link individual Test Case IDs to the Story/Bug in JIRA projects.
76 votes -
Sync attachments from ADO to PRactiTest and Vice Versa
Currently we are not syncing the attachments from ADO requirements or bugs to PractiTest nor from PractiTest bugs to ADO. It would be great if we can do a 2 way sync for the requirements as well.
Many times the big requirements have attached docs which are essential for a tester to see to create test cases.
Bugs in ADO will have screenshots and log files attached and they need to sync across to the PractiTest as well.
Also when a bug is created from PractiTest to flow thru to ADO it will/should have screen shots attached along with other…22 votes -
made Entity visible in the dashboard list.
I would like to see Entity, Field and Filter in the dashboard list. Currently, it is not seen so I cannot determine whether the dashboard is pulling info from Test, Test Set, Instance, etc. I have to click on each one to look. Having it in the list would make things easier.
1 vote -
Ability to sync the comments from requirements and bugs from ADO to PractiTest and vice versa
Currently when the requirements and bugs are synced from ADO, the comments are not synced.
For requirements the comments have valuable information reflecting the changes and doubts which are important for a tester to know while creating test cases so it is very critical to include the comments as well.Also if a tester has certain doubts on a requirements if there is a 2 way sync he can just post the comments on the PractiTest and they should flow to the linked requirement card in the ADO.
For bugs, since the developers won't always have access to PractiTest, the will…
28 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
- Don't see your idea?