25 results found
-
0 votes
-
0 votes
-
Fix test set to use full width of any monitor (as it did before new UI)
Lots of people on IT uses large width monitors, and before the new UI was possible to really take advantage of it on test set, considering number of columns and wide data.
After the new UI the test set displays on the middle of my monitor, with two giant empty blocks on the sizes (left and right), and now my columns are smaller and I'm no longer able to read all my information. It got worse! Very bad!
Please, please, fix that ASAP!
6 votes -
3 votes
-
Improve multi-level bullet list formatting in rich text editor
Currently, rich text editor poorly supports multi-level bullet points, in addition, the formatting looks completely different when creating and when running a test in a test set: making a multi-level list a single-level list
12 votes -
Add the ability to recognize duplicate test cases
As a user, I want to know if my library contains duplicate test cases
1 vote -
Ability to add 'Id' as a column for requirements distribution tables
As a user, I want to be able to show coverage by specific requirements in the dashboard
0 votes -
1 vote
-
Remove auto filter limitation
Support the option to create more than 50 auto filters per module
0 votes -
Support for auto filters for more than 2 levels
Allow to create auto filters on more than 2 levels
0 votes -
The ability to sort filters by column on the "All Filters" page
The ability to sort filters by column on the "All Filters" page.
For instance, we currently have 9 pages of filters on PractiTest project, so it's difficult to find specific filters or categories on that page.5 votes -
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 -
include the ability to add tests all at once instead of individually when adding tests on the traceability tab in requirements.
We often add 10 or more test cases to each requirement which means having to click "Add" that number of times to link each test case. It would be nice if there was a way to add all of them at once.
1 vote -
9 votes
-
Provide the option for the Parameter checkbox to be populated by default
When adding in the parameters there is a checkbox that is unpopulated by default. To enter a value in the parameter field, this needs to be checked.
Although in isolation it is a small thing to have to click the checkbox each time, it soon builds to a significant irritation when preparing multiple test cases15 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 -
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 -
Test case templates
Allow creation and selection of test case templates. These could have standardized titles, step names, etc. Example:
Title: "My App: <component>: <test>"
Step 1: "SETUP"
Step 5: "CLEANUP"20 votes -
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 -
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
- Don't see your idea?