585 results found
-
Linked List Add New Item in drop down
Allow addition of new items to a linked list child list from the form drop down. This feature was added to regular lists a while ago and is much more convenient then modifying the list contents in the fields settings section.
1 vote -
Reorder Test Cases in Test Library & preserve the same order when generating the reports.
The user should able to reorder the Test Cases for a project in the Test Library.
My requirement:
I have 3 tests,
Test 1, Test 2, Test 3They are created in some order say, Test 1, Test 2 , & then Test 3,
But my Test 3 is the continuation of Test 1, what I actually meant is Test 3 will start from where I ended in Test 1.
So, I want my tests to be in the below order:
Test 1
Test 3
Test 2I tried several ways to reorder the tests but nothing worked.
Some of…
12 votes -
I would like there to be a way to batch delete the tests from multiple testsets
I would like to have the option to batch delete all the tests within multiple TestSets. Alternatively, if I clone multiple TestSets, I should have the option to delete the tests within the new cloned TestSets
1 vote -
link requirement to requirement
Ability to link a requirement to another. This can be another option in Traceability tab where we currently link tests and issues.
7 votes -
Versioning test cases
Feature to versioning of test cases, allowing comparisons of differences and return to previous versions.
69 votes -
create a way to filter/report on issue status history
I am looking for an easy way to report on the status history of an issue. As it is now, I can only easily filter on current status when I create reports/filters. I am looking for a way to find issues that were ever in rejected status or were at one time set to "reopened" without having to manually read the history of every issue.
1 vote -
Task Board - Customize with chosen fields
I would appreciate to be able to choose the fields shown for all tasks. For exemple, to be able to see the Priority or other chosen fields.
10 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 -
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 -
9 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 -
Create multiple issues by sending one request
I see it is possible to create one issue only by sending one request. I would like to create multiple issues in one request.
2 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 -
Adding a What Change options to Reports
Creating a daily report to see what test cases have been changed, so that we can keep our testsets up to date with the new changes in the library.
adding what changed as a report option would simplify the work flow of opening up Project History
1 vote -
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 -
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 -
Improvements to Exploratory testing
When using Exploratory testing can we have an option to:
(1) Take screen shot and add comments via the tool itself
(2) record all the screen actions as a recording.
(3) Convert all the actions automatically as steps if you want to make the test a scripted one for later use26 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 -
Different types of parameters
Currently we are running into a wall with re-usability. Either we don't use parameters,and there's no re-usability and alot of cloned code for one single functionality, or we use parameters and every test with "Call steps from another test" will have to set up all the parameters on test set run.
I propose a way to set parameter values on a test level. So when we use "Call steps from another test", all the parameters for that called test are possible to be set from within the current test, allowing for a lot more re-usability within tests. Not all should…
5 votes -
Add descriptions to the fields (custom or System)
When we create custom fields or modify a System field, it would be great to add a Description that we could then view as a tool tip in the entity. This would give more context around the importance or purpose of the field and would give testers a more compelling reason for filling it in.
Right now, we document the purpose and description of each of the fields and filters we have set up in a wiki page. It would be nice to be able to manage this directly from PractiTest.
1 vote
- Don't see your idea?