Skip to content

General

General

Categories

8 results found

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

    60 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)
  2. We would like to have execution progress graph displaying custom fields.
    example:
    a execution graph with ("automated", "planned for automation",...) fields.

    40 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)
  3. 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…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. When a project is integrated with a project board in JIRA or in future ADO, can we please make sure :
    (1) All the requirements flow thru automatically without a manual need to do it
    (2) The syncing of the requirements is automatically done periodically.
    (3) The issues raised in the Jira or ADO should sync automatically.

    26 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. Currently we are not syncing the attachments from ADO requirements or bugs to PractiTest nor from PractiTest bugs to ADO. It would be great if we can do a 2 way sync for the requirements as well.
    Many times the big requirements have attached docs which are essential for a tester to see to create test cases.
    Bugs in ADO will have screenshots and log files attached and they need to sync across to the PractiTest as well.
    Also when a bug is created from PractiTest to flow thru to ADO it will/should have screen shots attached along with other…

    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)
  7. Currently we can create a 2 way integration with Azure Devops, but only if Azure is on Cloud.
    The integration with Azure Devops Server doesn't work.

    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)
  8. 0 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  ·  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?