Skip to content

General

General

Categories

603 results found

  1. Currently the API v2platform supports Delete method call for object such as Steps/Requirements/Tests/TestSets.
    As part of our work in the company we post automated runs results to the run data of an instance and sometimes it accumulates a huge amount of runs in the history which slows down the retrieval of data via the Practitest platform.
    so it would be nice if we could delete the runs from the history either bulk deletetion or by ID

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

    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)
  3. For example, users using AzureAD would like to have automatic sync between PractiTest and AzureAD users.

    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)
  4. standard .net test runners can produce .trx files e.g.

    vstest.console.exe /logger:trx foo.dll

    dotnet vstest --logger:trx foo.dll

    These are just XML files. We currently have to parse these xml files and perform hundreds of individual uploads, waiting 60 seconds every time the server throttles with HTTP 429

    It would be better if .trx files could just be uploaded to practitest to produce a run of a test set, and the parsing was done on the server.

    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)
  5. When you prepare data in Multilist, there should be easier option to select them in filter preparation.
    Actual:
    Set up multi-list field (eg. task number for functions) and prepare TCs with these numbers.
    Prepare filter with multiple values - you have separately prepare filter or you have to click "Or", "open dropdown", "select value" repeatly.

    Expected:
    Use shift/ctrl to select multiple values from multilist.
    There should be displayed filed with selected list.
    Clicking on field opens dropdown with selected values for editation of multiselection.
    "X" will be over whole multiselection and delete whole selection

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

    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)
  7. Ability to link a BR to the FRs that supports the BR.

    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)
  8. Include comments in the PractiTest API.

    17 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)
  9. Currently get an automated email with a link to click to download the report. I would like the report downloaded automatically.

    E.g. If I could anticipate the link to download the report (as currently added to the email) I could generate it automatically and hence download the report. You might also provide an api style interface such that the report is available in chrome as a page which can be extracted from chrome as JSON.

    P.s. Not a good solution for me, but still a solution, have you thought about a google drive interface for the reports (and exports) 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)
  10. 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)
  11. 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…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  12. As a company with many related projects that are reported to the same channel, we have a need for distinguishing between the tests belonging to different projects

    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. Hi Admin,

    while running of an instance, it had better provide a status 'SKIP‘ so that we can know how many test cases 'SKIP' in regression testing.

    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)
  14. Similar to JIRA headers.
    Ex: A dynamic todays date added to current release.

    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)
  15. Hi, While we integrated API into our testing pipeline, noticed that it could not create / modify dashboard via API.

    Suggest to support this feature.

    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)
  16. If we know of a particular release date and we want to track test execution to that date, then a burn up report can help us track and highlight risks at a very early stage.
    This should take into account the testers available for the execution so that it can work out the velocity accordingly

    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. Currently you can select "Run" and start from scratch, but no way to continue from where you left off.

    19 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)
  18. Hello,
    Attachements are quite painful to add: this is click-click-click ... We should be able to add images or documents in the description. Images would appear in the description, so we wouldn't have to re-click to see it real sized.

    Additionnaly we don't understand why we can't see the description of the test while executing test cases . Is it intentionnal ? Thanks !

    7 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)

    The option to drag & drop files into the description will be supported in the new forms UI we are working on these days. The test set / Issues form already have this option - soon all items will have it as well

  19. NARRATIVE: The "Goto Tests…" field currently only works for test IDs. It would be nice to be able to go to tests by test name as well.

    STEPS TO DUPE:
    1. Go to the Test Library module.
    2. Type an existing test name into the "Goto Tests…" field
    3. Push return.

    RESULT: All tests for the currently selected filter are displayed.

    EXPECTED: To go to the test with the matching name.

    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)
  20. I would like to see Entity, Field and Filter in the dashboard list. Currently, it is not seen so I cannot determine whether the dashboard is pulling info from Test, Test Set, Instance, etc. I have to click on each one to look. Having it in the list would make things easier.

    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?