613 results found
-
Make reload of this page only on demand
Reload of select should be done only on demand - it takes too much time to wait each time just after pressing 'Back' on browser...
1 vote -
1 vote
Ido Tandy responded
-
Add bulk of test to a requirement tractability
in the same mechanize as add test to a test set, instead of picking them one by one like today
5 votesIdo Tandy responded
-
Option to cascade view in filters
add option to cascade a view of a parent field to all of its children
1 voteIdo Tandy responded
-
Able to move ALL the fields on the panels, not just the customized fields
Would like to be able to move any of the fields on the panel not just the customized fields to a different location.
2 votesIdo Tandy responded
-
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 votesIdo Tandy responded
-
4 votes
Ido Tandy responded
-
Hide \ unhide passed steps
When running testset, some of steps may be blocked\failed\skipped. it will be helpful if you could hide passed steps and see only who need a second review.
1 voteIdo Tandy responded
-
Clone parent folder structure to child project if does not exist
As a practitest user, I want to clone my test cases and attributes, specifically folder location.
Acceptance Criteria:
If the folder structure does not exist, create the folder directory (a unix example would be mkdir -p /root/parent/leaf where if only /root exists, the rest of the directory is created.
Provide an option not to create and place in the folder structure13 votes -
Support creating filters on 'Instances'
Currently filter Types supported: Issue, Test, TestSet, Requirement. Can you also please add 'Instance' to the filter type support. We include quite a few custom fields on our instances and it would be nice to create a filter using these custom fields for all the instances.
14 votesIdo Tandy responded
-
Improve Jira Integration
We think the following would improve the Jira integration tremendously if implemented:
- In the auto generated issue description (when clicking fail & issue) include the expected resultMake linking existing issues less cumbersome. At the moment users need to:
1) Add the ID
2) Navigate to the issue
3) Edit it with the pt_id
4) refresh in the step
This should all ideally done by PT (itself + the Jira plugin)Full 2 way integration: add a tab in Jira that lists hyperlinks of all the linked PT tests (other tools such as QMetry do this)
6 votesIdo Tandy responded
-
Convert "Step Expected Results" to a Pass/Fail checklist format.
By making Step Expected Results a Pass/Fail checklist so a user can check off the results as they go.
It would also be nice if these Expected Results are stored in a library for use in future test steps as well.
This increases test accuracy and allows for a more efficient management of expected results. Also, in the event of a bug, you can automatically report exactly which expected result was not met.
This will greatly reduce time and energy spent by the development team trying to figure out exactly what failed to occur.
3 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 votesIdo Tandy responded
-
Redmine 2-way integration: Allow viewing and editing bugs from Practitest
When using the Redmine 2-way integration, currently users need to go back to Redmine in order to see the bug list or in order to edit the bugs.
It would be very helpful if Practitest users would be able to view and edit the bugs from the "Issues" tab or even view them on the different dashboard widgets.
3 votesIdo Tandy responded
-
provide different indication for fixed/close issues
In case an issue related to test we will see a "green bug" indication.
I think for better test planning you should provide different indication for open/fixed/close issues so I will now if to run this test and its priority.Generally better correlation between Issues and test sets is needed.
2 votesIdo Tandy responded
-
1 vote
Ido Tandy responded
-
Allow WYSIWG input - currently if you cut and paste requirments, test cases, etc, you get erroneous characters in the text.
Allow the cut and paste of information from Word, Excel or any othe non-8 bit editior.
6 votesIdo Tandy responded
-
add the ability to view Requirements in Tree View from Test Library Traceability on click of Show Requirements
We use parents in our requirements so from Requirements I always view as a Tree. When I am in a test case and click the Traceability tab to link to a requirement and I use "Show Requirements" it only shows me a flat list in ID order so I have to maintain an XLS cheat sheet to add so I can see in tree view. It would be a GREAT enhancement to PractiTest to be able to choose Tree View from the Test Case Traceability tab on Show Requirements and save me a ton of time. Thanks :)
4 votesIdo Tandy responded
-
1 vote
Ido Tandy responded
-
Defining custom views per a mandatory field test cases have
Say you have a mandatory field named 'Feature' in test cases. You might want to create a view named Features according to the value the Feature field has.
Currently you have to specify a view for each value of Feature.
Moreover, if you have a new feature, you have to add it manually to the filter.0 votesIdo Tandy responded
- Don't see your idea?