Skip to content

General

General

Categories

606 results found

  1. 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
    0 comments  ·  Admin →
    How important is this to you?
  2. Similar to JIRA headers.
    Ex: A dynamic todays date added to current release.

    1 vote
    0 comments  ·  Admin →
    How important is this to you?
  3. 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
    0 comments  ·  Admin →
    How important is this to you?
  4. Similar to Preconditions in Test Run, add a field Test Data that shows up while running a test

    3 votes
    How important is this to you?
  5. 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
    0 comments  ·  Admin →
    How important is this to you?
  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.

    70 votes
    started  ·  2 comments  ·  Admin →
    How important is this to you?
  7. 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.

    76 votes
    How important is this to you?
  8. 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
    How important is this to you?
  9. 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
    0 comments  ·  Admin →
    How important is this to you?
  10. 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
    planned  ·  0 comments  ·  Admin →
    How important is this to you?
  11. There are many cases where "Login as.." for instance is just called by other tests so that is not repeated in every Test, These "Login as" Tests are necessary but not necessary in the TestSets. Could a small check box, "Do not include in TestSet" be added so when we create a TestSet the Unnecessary tests are not visible or Color Coded to let the Tester know that Test is not needed in the TestSet? We are currently using xx as a prefix in the Test Name to distinguish these types of tests. Love your product!

    3 votes
    0 comments  ·  Admin →
    How important is this to you?
  12. The test execution progress graph is a real good tool, giving clear info on a project progress status.
    For now the time period of this graph is fixed to 28 days.
    Being able to customize this X-axe would be very useful to study the reasons of slowliness in a project afterwards, for instance.

    8 votes
    1 comment  ·  Admin →
    How important is this to you?
  13. You should give the users to add fields at test step level.

    They should be allowed to Add things like Test Data for a particular step like Large Queries it it. For us the Test Precondition or Test Description or Test Name cannot be used for that purpose.

    13 votes
    1 comment  ·  Admin →
    How important is this to you?
  14. When Practitest generates a 'detail' report of tests, in Excel format, there are two blank columns on the left (A & B) and a lot of blank rows padding the report. These blanks waste space on the screen/ sheet when printing. I have to manually remove these every time, which wastes time. Please could you take them out of the default report ?

    8 votes
    1 comment  ·  Admin →
    How important is this to you?
  15. I want to get the steps of test cases which are in Automation status (Automation filter).

    3 votes
    0 comments  ·  Admin →
    How important is this to you?
  16. 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
    How important is this to you?
  17. There should be an option to allow the user to clone either as anew Test Set or with existing Test Status.

    It will help us to run the same test set with multiple versions of our product.

    Currently cloning reset all the test statuses.

    3 votes
    0 comments  ·  Admin →
    How important is this to you?
  18. 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

    26 votes
    1 comment  ·  Admin →
    How important is this to you?
  19. 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
    How important is this to you?
  20. 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
    How important is this to you?
  • Don't see your idea?