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.

566 results found

  1. Add number of tests in each folder in folder view

    In the folder view from tests you cannot see how many tests are inside a folder until you click on it. It would be good to see the count in the folder view

    1 vote
    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. expend the search feature when adding a test to a test run

    When adding tests to a test run you can either select from the entire list of tests or run a pre made filter. It would be nice if this had a few more options such as:

    • Free form search
    • Select Tests from an existing run
    • Pick a Folder to add tests from
    2 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. 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

  4. Overall, Practitest should remember and persist column widths and sorts

    There are no pages in PT that actually remember the width of columns or sorts. This makes using PT pretty annoying for people who manage or run test sets, issues, or requirements.

    61 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…)
    started  ·  4 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. 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

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

  7. Add / Delete multiple steps with a single click

    PractiTest is rather click-heavy.
    One way to reduce this would be to allow multiple steps to be added quickly. A data entry field before the Add Step link allowing the user to provide a number of steps to be added would be a simple fix. Default this to 1 and existing behaviour remains. If the user enters 23, then 23 new blank lines are added/inserted. This will facilitate faster/less disrupted test case writing.

    As the user may then over estimate the number of blank steps required, an option to Delete all blank steps would be a complimentary click reducing feature.

    8 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

  8. Add "Pass all Steps" button to the bottom of each test

    1 vote
    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. 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

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

  12. Add "Automation" checkbox to filters

    It is not currently possible to filter test cases based on the "Automation" checkbox on the test case. Please add the ability to filter test cases by that element.

    13 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

  13. Allow automated test runs to be passed manually

    Currently, if a test is marked as an automated test ("Automated" checkbox is checked on the test case) the status of the test run cannot be changed manually. At times a test will fail due to an issue with the automation script itself, so we get a false fail. At that point we will run the test manually, but then we are not able to fix the status in Practitest.

    22 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. Not auto-enable bookmark panel in PDF reports....

    Since there are no bookmarks created in the PDF versions of PactiTest reports anyway.

    1 vote
    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. 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

  16. Add a field type that can store more than 256 characters

    The subject says it all -- this sort of field would be useful were some amount of explanatory text is needed (such as describing prerequisites/preconditions for a test).

    1 vote
    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. Allow times to be shown as either a 12-hour or a 24-hour clock

    1 vote
    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. When updating an issue some values update instantly disregarding "Back to Issues" while others do not

    Open an issue
    Insert a title
    Save changes
    Re-open issue
    Editing the title and pressing "Back to Issues" will cause a confirmation box to appear asking you if you are sure that you don't want to save, pressing "No" will make sure that the changes are not saved.
    Changing the "Status" to "Rejected", adding attachments or comments will instantly save even if you press "Back to Issues" and choose "No" at the confirmation box.

    Expected result: Every change made will only save if you choose "Yes" at the confirmation box

    Actual results: Results are inconsistent, some values change instantly and…

    1 vote
    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. Filters by users which are no longer part of this project

    Filters by users which are no longer part of this project

    4 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. Option to remove 'title' field for every test step

    Although a small issue, this becomes irritating when we are creating or importing dozens of test cases.
    The 'step title' field (it doesn't actually have a name) adds an extra step which seems unnecessary. In my experience it is rare to need to title each and every test step. Please could you have the more standard Description-Expected Result only format when creating test steps?

    5 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
1 2 … 23 25 27 28 29
  • Don't see your idea?