615 results found
-
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 votes
Ido 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).
39 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
-
Settings - custom view: add the option to sort or filter the custome views list
When there are many views (as being recommended by PractiTest) it is hard to manage them in the custom view list table.
By filtering and/or sorting this table (by type, name, owner..) it will be easier to use1 voteIdo Tandy
responded
-
Ability to copy a Custom View within a project at different levels for one module.
e.g. I have created one Custom View as 'View1' which has several child custom views such as 'View1.1','View1.2'. Now i create another custom view below 'View 1' as 'View 2'. Having the ability of simply copying 'View1.1' and 'View1.2' under 'View 2' would save lot of efforts for users. Especially if you see your project having number of similar tasks being created under it repeatedly.
10 votesIdo Tandy
responded
-
effort/Time estimation against tests which sum to requirement estimates
Time estimation against test duration which sum at the requirements level to see how long it will take to test the entire requirement
1 voteIdo Tandy
responded
-
Show which tests\steps in test didn't run on report
If you run a testset and didn't finished him you won't be able to find out that unless you enter the specific testset, into a test and see which steps didn't run at all. also, you won't be able to know if a test is fully run - you can make only one step within test and exit - when you enter the testset you got indicator of the status of the test, but you can't tell if all steps are checked.
1 voteIdo Tandy
responded
-
fixed
Add fixed date to view. When I want to know how many issues was fixed this month/week/day, I must have the fixed date in the view. Now, I have only created date and closed date.
1 voteIdo Tandy
responded
-
Change the way custom view filter is presented
If you add a custom view filter where two conditions both need to be true (A and B) the editing screen does not make clear that there is an implicit AND operator. In fact each line has the word OR at the end of each line. It would help if this part of the screen were redesigned to make the AND explicit and not show OR.
1 voteIdo Tandy
responded
-
Memorize show/hide selection when selecting tests for a TestSet
When editing a testset usually you have to navigate through a number of test listing pages of a specific view you have already selected. When you are doing this, the most comfortable setting is to hide the views box because the box is only taking space you need to fully read the tests names. However, each time you change between pages, the views box is made visible again (which is very annoying). I propose you keep the state of the views box when the page is changed. If it is hidden, then it should stay hidden until you need it…
3 votesIdo Tandy
responded
-
Add the number of tests found under each father and son
Means folders and sub folders, in both “Folder” and “Views” tree-views.
1 voteIdo Tandy
responded
-
display explanatory text with issues
When you assign a priority or severity to an issue it is important to know the definition of the categories (high, medium etc.). These could be different for each project. Could we have the facility to put some explanatory notice onto the screen where you log an issue? Perhaps it could be a type of project field (similar to memo) but with default text that is set up by the administrator and cannot be changed by the user. Even better would be to have something to click on (like a help symbol) to pop up the definition.
1 voteIdo Tandy
responded
- Don't see your idea?