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.

    83 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. 60 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  1 comment  ·  Flag idea as inappropriate…  ·  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. 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.

    60 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    55 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    planned  ·  Christine responded

    Hi,

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

    Best regards,
    Christine

  5. Feature to versioning of test cases, allowing comparisons of differences and return to previous versions.

    49 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    42 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    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  ·  2 comments  ·  Flag idea as inappropriate…  ·  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. The ability to find a certain word/variable and replace all instances of it in one go. Should also have the ability to change some of the instances and not all (maybe you could skip to each instance similar to the find feature on Mac when in a window and you press Command + F and then use the arrows to skip to each instance)

    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  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    33 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  19. Currently when the requirements and bugs are synced from ADO, the comments are not synced.

    For requirements the comments have valuable information reflecting the changes and doubts which are important for a tester to know while creating test cases so it is very critical to include the comments as well.Also if a tester has certain doubts on a requirements if there is a 2 way sync he can just post the comments on the PractiTest and they should flow to the linked requirement card in the ADO.

    For bugs, since the developers won't always have access to PractiTest, the will…

    28 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  20. When preparing a "Test set", sometimes we need to give extra informations about the "Set" we prepare with other builders and testers.
    It would provide us the ability to share informations such as the purpose of the "set" or any extra data needed to execute the test.

    And more, having a "comment" section in each "Set" would be helpful to share informations between testers and those who build the "Set".

    26 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 →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
← Previous 1 3 4 5 25 26
  • Don't see your idea?