515 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.
63 votes -
Overall, Practitest should remember and persist column widths and sorts
There are no pages in PT that actually remember the width of columns or sorts. This makes using PT pretty annoying for people who manage or run test sets, issues, or requirements.
55 votesNew grid implementation, including the requested functionality, will soon appear as a Beta feature.
-
Versioning test cases
Feature to versioning of test cases, allowing comparisons of differences and return to previous versions.
49 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.
48 votes -
Add the ability to view Test Steps directly from Test Sets
Now, the only thing we can do to view Test Steps from Test Sets is by:
1. Clicking the instance
2. Click "Test in Test Library"which means we can only see steps for a particular test at a time.
I'd suggest that you add the ability to view Test Steps directly from Test Sets, maybe by implementing display popover? Or maybe add another page that allows us to view all steps in all the tests in a certain test set. Thanks!
41 votes -
Add sorting to change the run order of the tests in a TestSet
I would like to be able to reorder tests in a testset more easily, and preferably in bulk.
Generally I want to arrange the tests by component, or tester, or ID; all of the useful sorting options I can think of are currently available as column headers.
It would be very useful to have a sorting feature which would allow quick reordering by column headers. For example, sort by tester and then component. Whith that, each tester can click "Run" on their first test case, and PractiTest would go through their tests, in order of component.
A simple option would…40 votes -
Link test to test
Please make it possible to link test cases between each other
40 votes -
Allow to select from used tags when entering Tag as filter criteria
When creating filters and tag is selected as filter criteria - choose from list of used tags (select with search) to avoid spelling mistakes
39 votes -
Save search as filter
Add ability to convert a search to a filter (which can be later customized).
37 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.37 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)36 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.
34 votes -
Add the ability to sync all the standard information sections and fields from ADO to PractiTest & vice versa
Current integration with ADO is only syncing the Description information section from ADO to PractiTest but in most cases there are multiple information sections depending on the Work Item type in ADO like Acceptance Criteria for requirements and Repro Steps, System Info and Acceptance criteria for a bug in ADO. It will be great if the syncing is not limited to just Description information section but is smart enough to sync all the information sections to PractiTest when the sync is done.
Also there are other important fields like Release Date and Priority for the Requirements which must be synced…33 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…
31 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 -
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 -
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.
26 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 -
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 use25 votes
- Don't see your idea?