564 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 -
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 -
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 voteIdo Tandy responded
-
4 votesIdo Tandy responded
-
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 -
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 -
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 -
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 -
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 -
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 voteIdo Tandy responded
-
1 voteIdo 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 -
Save search as filter
Add ability to convert a search to a filter (which can be later customized).
38 votes -
Improve Fogbugz Integration (Push data to and from Pracitest)
(1) link test cases to externally stored requirements (In fogbugz) and push the externally stored requirement data into Practitest requirements for reporting/dashboard.
(2) Add a Push link next to the Defects field in the Test Run Result screen which pushes a bug report to the external system (FogBugz) without leaving Practitest and make a copy in 'Issues' at the same time for reporting/dashboard.
(3) Hyperlinks to externally held data if only linking to issues/requirements in the external system and not pushing data to and fro (hovering the mouse cursor over a fogbugz case ID in either issues or requirements screen…3 votesIdo Tandy responded -
Report Center: Missing a free text area for a sub title
(Short report description/summary to be added manually by the reporter)
0 votesIdo Tandy responded -
Non-critical Step
Add ability to define a step as a non-critical step, and thus a failure on this step would not fail the test.
3 votesIdo Tandy responded -
hierarchy
Add ability to copy a hierarchy from one project into another.
1 voteIdo Tandy responded
- Don't see your idea?