614 results found
-
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 -
Versioning test cases
Feature to versioning of test cases, allowing comparisons of differences and return to previous versions.
72 votes -
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 -
Github with Two-Way Integration
Please add two-way integration with Github. Not everyone's on Atlassian products such as Jira, Bitbucket, et al.
40 votes -
execution progress graph with costume fields
We would like to have execution progress graph displaying custom fields.
example:
a execution graph with ("automated", "planned for automation",...) fields.40 votes -
Make the test name fixed (frozen) when scrolling/editing test steps
can you add the test number to the top banner of the page? or make the test name and number line "sticky" so it will stay visible when you scroll down?
(When I have few tests open, in order to work in parallel - I have to scroll up all the time to make sure on which test I'm on.
very annoying... and leaves too much room for errors (=unwanted editing)38 votes -
Allow Bulk Edit to Edit ALL tests in a Test Set, not just 100 at a time
If you want to do a bulk edit of a field for the tests in a test set you are limited to what you are allowed to see on the page (max 100 now). If I have a few hundred I currently have to go to each page and do a bulk edit. What is even more tedious is after I do one it resets back to 1-100 so I have to first double check I did it correctly for say 201-200, etc. This functionality is available when doing bulk edits of tests (where it asks if you would like…
36 votes -
Include pictures / attachments in reports.
It would be nice if there was a way to include photos and attachments that are included in test in the final report for reference. It can be odd at times to have a test that references a picture or attachment and it does not show up in the report.
34 votes -
make requirements links visible when executing a test
When executing a test case one of the key things you'll want to reference are the requirements, so logically they should be accessible.
33 votes -
Import Jira requirement ticket with all it's sub-tickets
In order to provide better coverage of the specifications I do propose to implement:
- Tree-like import that means importing parent and subtickets;
- Provide straight dependence between subticket and linked test, i.e. if Practitest user link test to subticket the test should also be linked to parent ticket automatically, as subticket is a must part of parent;
- Add system field "Traceability" for requirements that will reflect clickable test IDs;
If the solution will be implemented it will simplify test covering process and test covering tracking process;
28 votes
Ido Tandy
responded
-
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 "+" and "-" for edited test case in history log
It would be better to see the changes in the test case history log when the test was updated by adding "+" (for addition) and "-" (for removal) signs in front of each change
27 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 -
Improvements to syncing requirements or bugs from Jira or ADO
When a project is integrated with a project board in JIRA or in future ADO, can we please make sure :
(1) All the requirements flow thru automatically without a manual need to do it
(2) The syncing of the requirements is automatically done periodically.
(3) The issues raised in the Jira or ADO should sync automatically.26 votes -
option for cloning traceability (linking between requirements and tests)
Whenever I need to clone Tests or Requirements I have to do double work of adding back linking between entities an option for cloning not only attachments but also linking between Requirements and Tests would help.
26 votes -
Ability to add a test case to a test set by writing the test number/range
As mentioned with the Ability to add a test case item, we tried filters; it’s cumbersome to have to shift gears and create a new filter every time that we want to look up / search for something new. It clutters things up as then there is the maintenance and scrolling to contend with as well.
26 votesIdo Tandy
responded
-
Add requirement link to an issue when posted to Jira
When an issue is created from a test, the associated requirements could be linked (if Jira requirements, then the Jira requirement link) to the issue document (perhaps appended to description, or to a field defined in Practitest by the user) before being sent to Jira.
Why? So in Jira a developer can click straight on the requirement to see what should happen, rather than dig through a number of screens to access the requirement26 votes -
Suggestion on the "Call to test" feature
The feature "Call To Test" brings some limitations to us. I want to see if your team can provide some solutions or improvement plan. Thanks you!
- No tracability between parent test cases and the called tests
- Tester is difficult to trace the relationship between parent and the called test
- Cannot preview the called test steps in the test cases. The test case only show the title of the called tests
- It's time consuming to open the new tab to view cases one by one
- Suggestion: Preview by clicking a button
- Export test cases: Test cases exports with only the title…
24 votesIdo Tandy
responded
- No tracability between parent test cases and the called tests
-
Have option to add field or custom field to an item in dashboard
I'd like to have the option to select fields in items displayed at the dashboard.
Example, if i have custom field of priority/severity, i'd like to be able to add it to the items displayed at the dashboard item.
To be more specific, if i add an item with "Test" entity and "latest" item type, i'd like to see the test priority as well as the existing fields in the table23 votes -
2 way integration with GitLab would be a nice feature.
Many companies use GitLab and they would warmly welcome a 2 way PT integration. At our company we conclude projects. One is developed in Redmine, the other is in GitLab. It would be nice to use PT for both platforms with equal funcionality.
22 votesIdo Tandy
responded
- Don't see your idea?