General

General

Categories

  1. When reviewing tests cases, it would be useful to have a field to comment a step when a tester is reviewing someone else tests cases. This way, he can add comments without modifying the test case. In case of misunderstanding if the specification, from the reviewer, author of the test case can update the reviewer and doesn't need to rewrite the test case.

    73 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  ·  Flag idea as inappropriate…  ·  Admin →
  2. it would be very useful if we can duplicate the filters (instead of re creating them every time ) in case we need them in several places.

    69 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  7 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. We want to be able to create filters from the API
    this will allow us to group text sets created via a pipeline and better organize what tests where ran where

    64 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  4. 57 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    waiting for supporters  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  5. As a user, I need the ability to link the Test Set ID from PractiTest to the Story/Bug etc.with JIRA projects. Currently, the PraciTest - JIRA integration only supports the configuration to link individual Test Case IDs to the Story/Bug in JIRA projects.

    57 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  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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.

    53 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
    planned  ·  Christine responded

    Hi,

    We are planning to replace our grid where will be this feature.

    Best regards,
    Christine

  7. We would like the test history to be more detailed. Currently it only shows us what step was updated but not a comparison of the changes made. We would like to see what was changed and what it was changed to (before and after). This would be of tremendous help during an audit if anything were to come up.

    51 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    waiting for supporters  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Feature to versioning of test cases, allowing comparisons of differences and return to previous versions.

    47 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  ·  Flag idea as inappropriate…  ·  Admin →
  9. I would like to be able to reorder tests in a testset more easily, and preferably in bulk.
    Generally I want to arrange the tests by component, or tester, or ID; all of the useful sorting options I can think of are currently available as column headers.
    It would be very useful to have a sorting feature which would allow quick reordering by column headers. For example, sort by tester and then component. Whith that, each tester can click "Run" on their first test case, and PractiTest would go through their tests, in order of component.
    A simple option would…

    40 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  10. Please make it possible to link test cases between each other

    40 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  ·  Flag idea as inappropriate…  ·  Admin →
  11. When creating filters and tag is selected as filter criteria - choose from list of used tags (select with search) to avoid spelling mistakes

    39 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  ·  Flag idea as inappropriate…  ·  Admin →
  12. We would like to have execution progress graph displaying custom fields.
    example:
    a execution graph with ("automated", "planned for automation",...) fields.

    37 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    waiting for supporters  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. Add ability to convert a search to a filter (which can be later customized).

    37 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  14. Please add two-way integration with Github. Not everyone's on Atlassian products such as Jira, Bitbucket, et al.

    34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    waiting for supporters  ·  6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Please provide option to link a Test Set with a requirement. As of now we have to link one by one all the test cases for a requirement and its time consuming when we have big projects with 300+ test cases.

    34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Currently it appears that filters can only be created using OR statements that meet the same item type which can reduce the ability to find what you're looking for when your test library gets to be particularly large.

    For example I can create a filter that says:
    (Name is this or that) and tag is this

    And cannot make a filter with:
    Name is this or tag is this

    Or advancing even further to:
    (Name is this and tag is this) or (name is that and tag is that)

    It would be nice to be able to have this grouping…

    34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    waiting for supporters  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Now, the only thing we can do to view Test Steps from Test Sets is by:
    1. Clicking the instance
    2. Click "Test in Test Library"

    which means we can only see steps for a particular test at a time.

    I'd suggest that you add the ability to view Test Steps directly from Test Sets, maybe by implementing display popover? Or maybe add another page that allows us to view all steps in all the tests in a certain test set. Thanks!

    34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. can you add the test number to the top banner of the page? or make the test name and number line "sticky" so it will stay visible when you scroll down?
    (When I have few tests open, in order to work in parallel - I have to scroll up all the time to make sure on which test I'm on.
    very annoying... and leaves too much room for errors (=unwanted editing)

    33 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. If you want to do a bulk edit of a field for the tests in a test set you are limited to what you are allowed to see on the page (max 100 now). If I have a few hundred I currently have to go to each page and do a bulk edit. What is even more tedious is after I do one it resets back to 1-100 so I have to first double check I did it correctly for say 201-200, etc. This functionality is available when doing bulk edits of tests (where it asks if you would like…

    31 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Current integration with ADO is only syncing the Description information section from ADO to PractiTest but in most cases there are multiple information sections depending on the Work Item type in ADO like Acceptance Criteria for requirements and Repro Steps, System Info and Acceptance criteria for a bug in ADO. It will be great if the syncing is not limited to just Description information section but is smart enough to sync all the information sections to PractiTest when the sync is done.
    Also there are other important fields like Release Date and Priority for the Requirements which must be synced…

    27 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    waiting for supporters  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 25 26
  • Don't see your idea?