General

General

Categories

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

    27 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 →
  3. When executing a test case one of the key things you'll want to reference are the requirements, so logically they should be accessible.

    26 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 →
  4. In order to provide better coverage of the specifications I do propose to implement:

    • Tree-like import that means importing parent and subtickets;
    • Provide straight dependence between subticket and linked test, i.e. if Practitest user link test to subticket the test should also be linked to parent ticket automatically, as subticket is a must part of parent;
    • Add system field "Traceability" for requirements that will reflect clickable test IDs;

    If the solution will be implemented it will simplify test covering process and test covering tracking process;

    26 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 →
  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…)
    waiting for supporters  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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 →
  7. Right now, typing a word into "Tags" field will bring up tag suggestions, which is nice and useful, but it is case-sensitive at the moment.

    For example, if the tag is "Billing" and I type "bill" without uppercase on the first character, the suggestion will not come up. I have to type it with capital B for the suggestion to come up.

    25 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 →
  8. When using Exploratory testing can we have an option to:
    (1) Take screen shot and add comments via the tool itself
    (2) record all the screen actions as a recording.
    (3) Convert all the actions automatically as steps if you want to make the test a scripted one for later use

    25 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. As mentioned with the Ability to add a test case item, we tried filters; it’s cumbersome to have to shift gears and create a new filter every time that we want to look up / search for something new. It clutters things up as then there is the maintenance and scrolling to contend with as well.

    25 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 →
  10. It would be nice if there was a way to include photos and attachments that are included in test in the final report for reference. It can be odd at times to have a test that references a picture or attachment and it does not show up in the report.

    24 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    Hi,

    Thanks for your feature request.

    We are planning to add link attachments and names of image attachments to the new Reports.

    Will keep you updated.

    Best regards,
    Christine

  11. It will be useful for the users to have a option to copy whole steps (description & expected Result) from an existing test to a new one.

    22 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 →
  12. 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…)
    waiting for supporters  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. The feature "Call To Test" brings some limitations to us. I want to see if your team can provide some solutions or improvement plan. Thanks you!

    1. No tracability between parent test cases and the called tests
      • Tester is difficult to trace the relationship between parent and the called test
    2. Cannot preview the called test steps in the test cases. The test case only show the title of the called tests
      • It's time consuming to open the new tab to view cases one by one
      • Suggestion: Preview by clicking a button
    3. Export test cases: Test cases exports with only the title…
    22 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 →

    Dear supporters of the idea,

    Please let us know what 2 out of 5 requests listed are the most important to you.

    Please feel free to add comments to the idea (feature request).

    Thanks,
    Yaniv

  15. There is currently no API to generate report by test set ID. Generate report by test set ID would greatly enhance our automation process

    22 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 →
    under review  ·  Christine responded

    Hi Jennifer,

    Thank you for posting your feature request here.

    We will review it and update you as soon as possible.

    Best regards,
    Christine

  16. Whenever I need to clone Tests or Requirements I have to do double work of adding back linking between entities an option for cloning not only attachments but also linking between Requirements and Tests would help.

    21 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 →
  17. When an issue is created from a test, the associated requirements could be linked (if Jira requirements, then the Jira requirement link) to the issue document (perhaps appended to description, or to a field defined in Practitest by the user) before being sent to Jira.
    Why? So in Jira a developer can click straight on the requirement to see what should happen, rather than dig through a number of screens to access the requirement

    21 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 →
  18. For batch editing of Tests/Requirements I need to add values to my custom fields, but they get overwritten with the new value and information gets lost unfortunately!
    An option for adding values but preserving old values would help a lot.

    21 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 →
  19. I'd like to have the option to select fields in items displayed at the dashboard.
    Example, if i have custom field of priority/severity, i'd like to be able to add it to the items displayed at the dashboard item.
    To be more specific, if i add an item with "Test" entity and "latest" item type, i'd like to see the test priority as well as the existing fields in the table

    21 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 →
  20. Allow creation and selection of test case templates. These could have standardized titles, step names, etc. Example:
    Title: "My App: <component>: <test>"
    Step 1: "SETUP"
    Step 5: "CLEANUP"

    20 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 →
  • Don't see your idea?