561 results found
-
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
-
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
24 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 requirement24 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 table22 votes -
Allow automated test runs to be passed manually
Currently, if a test is marked as an automated test ("Automated" checkbox is checked on the test case) the status of the test run cannot be changed manually. At times a test will fail due to an issue with the automation script itself, so we get a false fail. At that point we will run the test manually, but then we are not able to fix the status in Practitest.
22 votes -
Create the ability to import parameters
Rather than having to copy and paste parameters in from a datasheet, it would be good if we could map the parameters for multiple instances of a test case to a datasheet and import them
eg Select 10 instances of a test case, click an 'bulk update parameter' button or similar, which can then map to an excel datasheet22 votes -
Allow report generation by test set ID
There is currently no API to generate report by test set ID. Generate report by test set ID would greatly enhance our automation process
22 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 -
option for adding new values to custom fields without overwriting old values
For batch editing of Tests/Requirements I need to add values to my custom fields, but they get overwritten with the new value and information gets lost unfortunately!
An option for adding values but preserving old values would help a lot.21 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 -
Autosave any change while editing
When working on browser it's always good to have Auto Save feature. you can by mistake click on backspace and actually get "back" on browser instead of delete your text. or even if your browser had any connection problem. I had problem when adding new steps. it can be very useful and relaxing to know that my work hasn't gone due to any problem.
20 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.
19 votes -
Task Board - Add Option To Continue run for Test set
Currently you can select "Run" and start from scratch, but no way to continue from where you left off.
19 votes -
Linked lists in filters
I have two suggestions about the use of Linked Lists in filters:
Suggestion 1. If I use a parent list in the criterion, the criterion of a linked list should show me only the values that are related to the parent list value.
For example, I have two fields
Feature - values A, B
Sub Feature - values (A) 1,2 ; (B) 3,4
If my first criterion is "Feature is A", and I start to create criteria "Sub Feature is..", then the dropdown list should show me only values 1,2. Currently it shows 1,2,3,4Suggestion 2: If I use the…
18 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 -
Add new value to standard or custom fields via API
In a context of automated test, it could be valuable to be able to append new values to fields already existent via API.
At the moment, we can only replace the entire Field with new possible values. And if something goes wrong, I feel like there's a high chance to lose information.
17 votes -
Reviewing Test Cases Support
Is there a way of making reviewing test cases easier?
We can mark the tests ready for review, but would be easy if we have some GUI support to add the review comments to the steps or description.
We don't have to rely on other tools to send review comments etc if it is supported in PT itself.
17 votes -
clone or copy views in the tests library
For example we have a view with a lot of child views and now We would like to create the same view but with a different parent filter. So we would like to clone the existing tree and modify it instead of creating it from scratch.
17 votes -
Allow users to rename auto filters
Auto Filters are a great idea, however, the default name limits their usage.
I know that the Auto Filter is unique on the same level of the hierarchy, yet, I want to let my Test Managers decide how to name them.Plus, there might be a confusing situation in which someone creates an Auto Filter and makes it private - then another user cannot create such Auto Filter at all and gets a "name is already taken" message, which is confusing.
16 votes
- Don't see your idea?