30 results found
-
0 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 -
Open issues per test set
Create a new tab (next to History) in the test set that shows a list of open issues linked to test instances in the test set.
The linked issues column is not useful when there are a large number of instances and the bold/faded text for the issue number is confusing.
A simple list of issues that can be sorted by priority lets me know what needs addressing and I can go into each bug.3 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 -
Remove the 8 items limitation for dashboard tabs
As a user, I want to create dashboard tabs with as many items as I need
0 votes -
1 vote
-
2 votes
-
Add the ability to auto link requirements to issues using the Jira integration issues auto sync
As a user, I would want the auto-sync of issues for the Jira integration to pick of the traceabilty linkages to requirements from the 'Linked issues' field in Jira automatically
0 votes -
Remove auto filter limitation
Support the option to create more than 50 auto filters per module
0 votes -
PractiTest newsletter and updates on landing page
We're getting newsletters via emails from your team. This is nice, but it would also be nice to get these news and updates when you're entering the platform.
On the landing page, you have the "Info and Tips" option, maybe we could get these updates there every month?
1 vote -
GUI Support
It would be appreciated if user could operate Dashboard items using the GUI operation. Since it makes easily to change dashboard item's position.
2 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 -
Create the ability to add multiple instances of a test case to a test set
When creating a manual parameterised test set, multiple instances of a test case need to be added. At present this needs to be done individually. It is suggested that there is an option to 'Add multiple instances' to the dropdown menu by the '+ Add selected tests' (underneath Add all test in view). This triggers an input box to appear where a two digit number can be entered, and all test cases ticked will be added that number of times
16 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 -
Should increase Pie Charts capacity in the same tab
We use a tab for each version and there, we have a pie chart for each build from that version.
At this moment, only 8 pie charts can be created in a tab.We would like to be able to add more Pie Charts, for better visibility of all builds from that version.
Currently, we can either delete old build pie charts or create a second tab for the same version, both which are not good solutions. After each version, we send a report with all builds from that version and a guest link for stakeholders to see the progress,…
1 vote -
Should increase Pie Charts capacity in the same tab
We use a tab for each version and there, we have a pie chart for each build from that version.
At this moment, only 8 pie charts can be created in a tab.We would like to be able to add more Pie Charts, for better visibility of all builds from that version.
Currently, we can either delete old build pie charts or create a second tab for the same version, both which are not good solutions. After each version, we send a report with all builds from that version and a guest link for stakeholders to see the progress,…
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 -
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 -
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?