39 results found
-
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 -
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 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 -
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 -
Allow the account admin the ability to create reports/dashboards across projects.
Dashboards and reports should be able to be created to report on multiple projects. If an organization is able to report on all the activity within Practitest, it will allow Executive Leadership the ability to see the entire workload of what is being processed via Practitest.
It really will show the immense activity accomplished during testing as a whole.
22 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 -
Conditional Mandatory Fields - If I have a field that is value X, then make one or two ther fields mandatory to fill in (or select).
Conditional Mandatory Fields - If I have a field that is value X, then make one or two the selected fields mandatory to fill in (or select). If value is not X then either grey out the fields or make the other one or two fields not required.
18 votes -
Able to create a single dashboard across mutiple projects
Would like to have a single dashboard that can cover multiple projects. As a manager of projects this would be highly benefitcial.
17 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 -
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 -
Make Attachment to precondition to be visible while running test in test set
Currently attachments added as Precondition are not accessible while running a test
9 votes -
9 votes
-
Add defect search functionality to Add Existing Issue to Test flow
When linking a defect to an executed (failed) test, you do not always remember the defect ID. This is an annoying way to currently link defects.
On the link existing issue step, it would help greatly if we could bring up a list of all defects and be able to sort and search them by date/title/description.8 votes -
Add the ability to add custom fields and modify columns for Test Instances Run History
Right now, we only have:
- "Run date"
- "Status"
- "Tester"whenever we look at the test run history for instances. It'd be neat to have the option to add custom fields so we can better track previous runs.
For example: I want to be able to add "Commit hash" and "branch" to test instances run history so I can see the last GitHub commit that was tested.
7 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 -
Add Collision detect on Test edition
We have encountered situation when I have edited the Tests while my colleague had it open and editing. I have saved the changes first and when he saved his, mine were lost. It is quite a big problem in distributed large teams. Please take a look.
5 votes -
Improve functionality of editing and updating tests from runs
I find the current functionality of updating your test while executing it a bit clunky. Now I do understand that it is meant for small changes where big test overhauls should only be done in the test Steps tab but still I think there are some improvements to be made.
1) If a step has been edited during a run, PT should ask the user if he wishes to 'Update Original test' before navigating away from the page. I find that I often update a step but forget to click the button to update the test at the end.
2)…4 votes -
"Always on top" header for runs screen
When you run the test, the data about the test itself is not seen when you scroll down with the steps - neither the name of the test, nor the preconditions and the link where you can hover and see the info about test.
We should have a fixed header with all this info.
3 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,…
3 votes
- Don't see your idea?