592 results found
-
Support multiple page edit in the test instance grid like we have in the test library grid OR batch edit for all instances in a filter
Support multiple page edit in the test instance grid like we have in the test library grid OR batch edit for all instances in a filter
3 votesIdo Tandy responded
-
make dashboard update upon opening.
I corrected a spelling mistake on a filter name. Re-opened Dashboard and found spelling mistake still visible. It only displayed the corrected view after I manually re-freshed Dashboard, I think there is an assumption that when you open Dashboard it will be up to date with current information not on be part way through a 15 minute cycle of updates.
1 vote -
to identify updates on requirements
I would like to be able to recognize updates when I am uploading requirements. So when I have uploaded for instance 10 requirements to Practitest by using a 1.0 version of an excel, and I update the document and do a re-upload of for instance a 1.1 version. I would want Practitest to recognize existing requirements and identify changed and new requirements. This would enable me to see what testcases are affected (and should be modified/ deleted) and what requirements need new testcases.
5 votes -
integrate PractiTest with requirements tools
This could be done by integrating with requirements tools directly or by integrating for instance by using Jira use cases & requirements (ideally integration with Jira should be used when Jira is then also integrated with a requirements tool like Jama).
This will help traceability and reporting on requirements through the whole development and QA process3 votes -
Create an option in the report center sector for generating a report with our companies logo as default at the right top corner
So when i go to the Report Center that it will be possible to upload our logo in a report.
6 votesIdo Tandy responded
-
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
-
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 votes -
4 votes
Ido 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
-
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 votes -
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
- Don't see your idea?