Skip to content

General

General

Categories

(thinking…)

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

564 results found

  1. 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 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  2. 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 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  3. 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 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  4. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  5. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    1 comment  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  6. 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 process

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  7. 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 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  8. Add date-based and "show most recent only" filter options to "Instance" report types.

    It would be very helpful to have a report shat shows only the most recently run test instance and exclude the older test instances for the applicable filter.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  9. Add page nav to bottom of test instances grid

    Very simple, quick fix. I like to view the maximum number of test instances at one time (100). But there are no nav controls at the bottom of this grid, so to get to the next page, I have to scroll all the way up to the top of the page to click the "Next page" button. Very annoying.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  10. Change test history so to show previous and updated value

    Test history currently only shows me the step name which was updated/added/edited. I need to be able to see specifically what a team member has updated - a 2 column page with time stamp, user name who updated, left hand showing what the value of a field was, and the right hand showing what it was updated to.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  11. Field data set on 1 screen and showing back on other screens

    For example:
    I have 1 Custom field browser (list) that have some values in it (Chrome, Firefox Safari etc.)
    I set that custom field on the screen:
    - Test
    - Instance
    - Issue

    When I Create new Test and I set the Browser: Firefox when im done with the Test --> Il Create TestSet & Instance = When im in the instance screen I see the Custom field Browser thats already filled in with 'Firefox' that I have selected in the screen Test.

    Start the instance and there is a Issue --> Create an Issue, Open the Issue screen and…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  12. Better test step UI for running and editing test cases

    Step result - Rather than just change the colour of the step name/heading, which gets lost in the links and other text above/below it, shade whole the step area/row.

    If step N has a result provided (pass, fail, block), and all the steps between step 0 and step N are blank, set steps ) to N all to Pass. This will reduce the number of clicks a tester has to do in order to work through running a test case.

    Allow a step to be flagged as "needing review" while the test is being run so it can be completed…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  13. Implement ways to manage the automation job queue

    Currently, there is no way to see what jobs (test runs) have been started or are in the queue to run. Furthermore, there is no way to cancel a job once it has started. Also, only entire test sets can be sent to the job queue, when there are many times when it would be beneficial to submit only a subset of tests in the test set. For example, when you want to re-run a failed test, there is currently no way to do that without executing the entire test set again.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  14. Add to the Report a simple metrics of the overall test progress

    To display the percentage of the total number of tests that have been executed (test marked as, Passed, Failed, Not Complete)

    i.e. 6 total tests, 2 marked as Not Complete, 1 passed and 3 No Run.

    Percentage Test Executed = 50%

    Along with metrics to capture the Test completed status (Passed Test Vs Total number of tests) as a percentage.

    i.e. 6 total tests, 2 marked as Not Complete, 2 passed and 2 No Run.

    Percentage Test Completed: 33%

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  15. Allow field 'Actuel result' inside steps to be mandatory

    Some results of a step are so important you need to be sure the tester have described the result. By do it possible to make this field mandatory you can manage this situation.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  16. Option to add text in Dashboard

    It would be useful to have some kind of text summary next to graph in Dashboard:

    Example: "this and that test was failed because issue-x (minor), but the build is still released."

    Could you please add this feature to the Dashboard?

    -Ossi

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  17. Add ability to set called test parameters from the parent (or calling) script

    The "Call steps from another test" feature works well for testing a matrix of parameter values. However it doesn't allow for passing in static, never changing values to called tests for the sole purpose of re-usable script steps and provide a single point of change (aka single point of maintenance).

    For example:
    * You have an portal based site which has several "apps" or sub-sites.
    * When a user logs into the portal the get presented with a dashboard page with links to each of apps.

    Ideally the tester would be able to create a single login script that can…

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  18. add ability to drag and drop to tests

    the user should have an ability to drag and drop his tests inside a filter in case he wants to arrange his tests in a prioritized order

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  19. Add the ability to search all the tests that has "call to test" of a specific test

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

  20. Add Status to Steps

    It would be useful to add Status on steps so that a single test can be divided in different steps which should be evaluated singularly

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    0 comments  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Christine responded

    Hi Fabrizio,

    Thanks for your feature request.

    Could you please clarify it?

    Thanks in advance.

    Best regards,
    Christine

1 2 … 9 11 13 … 28 29
  • Don't see your idea?