603 results found
-
Don't scroll to the top of the page when clicking the menu icon for a filter
When a filter name is low on the page and you click on the menu icon next to it, it scrolls you to the top, causing you to have to scroll back down the page to the filter.
4 votes -
4 votes
-
4 votes
-
Integrate steps parameters with FireCracker (and/or API)
BDD automation has a feature call "Scenario Outline", where you can define a table data for the test. This feature is based in step parameters.
PractiTest hosts also a step parameters feature, although the table data is defined at run time, unlike BDD automation, which is defined at test definition time
This can be solved with a custom field hosting the table data, where automation framework can retrieve it using the API, but the problem is when we try to create a run.
I have tried FireCracker with a Scenario Outline test and the report is not accurate because it…4 votes -
Add Ability to Convert Scripted Test into Exploratory
It would help if users could convert Scripted Tests into Exploratory. We only started using Exploratory tests in the past year so if we could convert Scripted tests into exploratory that would help.
4 votes -
Link Requirements via Batch Edit
When doing a batch Edit I would like to be able to link the requirement in the edit functionality. That will help streamline the process of tracing backwards and forwards, making managing these projects easier!
4 votes -
Need flexibility to reuse of existing filters instead of creating multiple duplicate filters at different levels
Need flexibility to reuse of existing filters instead of creating multiple duplicate filters at different levels
4 votes -
Allow to sort list field values in descending order
Currently, there is an option only to sort them in ascending order. If you need to sort them in reverse order, you can only do it manually
4 votes -
Linked Requirements in Requirements Traceability
Expand traceability in Requiremnets to include Linked Requirements., This will enable association between Business Requirements to Functional Requirements etc.
Also supports a heirachy of requirements (drill down).
It appears that the change would be relatively simple given the existing Traceability functions in Requirements for Linked Tests and Linked Issues. Just add Linked Requirements.
4 votes -
4 votes
-
Add custom run status
Enable ability to add custom run statuses. Most important ones needed by my team are "Work In Progress" (or WIP), "Deferred", and "Canceled".
4 votes -
When importing tests, enable the option to use "Call to Test" to existing tests
When I import tests with steps, just like I can "call" the test between the steps in existing Test, or one I'm creating manually, I'd like to have an option like that in Import spreadsheet.
For example, another Step column "Called Test ID" where I can put the ID of a test and it will be called.4 votes -
Add risk calculations to Issues
based on the issue severity and its probability enable users to sort by Issues risks
3 votes
Ido 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
-
Add some more filter options
Add more filtering options like: "has"(If a searched text is a part of the entire text), "greater\ less than"(for integers), "Doesn't have"(same as the "has" but the opposite), etc.
3 votesIdo 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
-
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
-
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
-
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 -
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
- Don't see your idea?