613 results found
-
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
Ido Tandy
responded
-
Add status for users in user setup
In current version the basis for access and invoicing is users defined in the user setup. In a project when testers are involved now and then, the administrator must manually remove the users to have control of the costs. When the users is supposed to do testing activities later, the admin must then manually add all users. This is very time consuming in big projects. However, it should be possible to set a user inactive by changing a status that will prevent the user from having access to the project and also will exclude this user from the payment.
1 vote -
Undo removed step
Please add the option to undo when removing step by mistake.
9 votesIdo Tandy
responded
-
Test Set table: User should be able to edit fields directly from table
Test Set table: User should be able to edit fields directly from table
2 votesIdo Tandy
responded
-
Set a default time zone for the account
When new users are added they are initially set up with the time set to UTC (GMT). For most users this is not appropriate and they need to go into settings to set their own time zone. This even applies to users in the UK who need to select London in order to get the daylight saving time applied automatically in the summer. If we could have the facility for an administrator to set the default time zone for an account then most new users would be set up with the right time.
4 votesIdo Tandy
responded
-
Editing option for cloned tests
Once we have cloned a set of tes cases can we have the option of going back to the batch and re naming the certain batch down the line.
1 vote -
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 votesIdo Tandy
responded
-
Rename the system generated Test Case ID
Have the ability to rename the system generated Test Case ID or allow this field to be "hidden". We use our own Test Case numbers and this is confusing for the testers to have two number fields.
8 votes -
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 -
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
- Don't see your idea?