Skip to content

General

General

Categories

560 results found

  1. 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)
    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)
  2. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  3. 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)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. 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)
    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)
  5. 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)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  6. 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)
    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)
  7. 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)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  8. 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)
    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)
  9. 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)
    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)
  10. 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)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  11. 1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  12. 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)
    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)
  13. 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)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  14. 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)
    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)
  15. When linking a defect to an executed (failed) test, you do not always remember the defect ID. This is an annoying way to currently link defects.
    On the link existing issue step, it would help greatly if we could bring up a list of all defects and be able to sort and search them by date/title/description.

    6 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  16. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  17. Now you have to upload an attachment twice when there are issues to raise. It would be handy if an attachment can be linked or copied to the issue.

    10 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  18. Currently, when you enter an existing test set, the Test Instance Name column is very narrow, cutting off most text of the test name. I constantly have to increase the Test Instance Name column EVERY time I reload the test set page. It's very annoying. At the very least, it would be nice if the column width would be remembered while I'm actively so I don't have to constantly increase it.

    13 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. 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
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  20. I find the current functionality of updating your test while executing it a bit clunky. Now I do understand that it is meant for small changes where big test overhauls should only be done in the test Steps tab but still I think there are some improvements to be made.

    1) If a step has been edited during a run, PT should ask the user if he wishes to 'Update Original test' before navigating away from the page. I find that I often update a step but forget to click the button to update the test at the end.
    2)…

    1 vote
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    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)
  • Don't see your idea?