Skip to content

General

General

Categories

613 results found

  1. We discussed it with Joel during his visit in Cambridge, UK. It would be beneficial to see Test Description on Test Set Run view (above the steps). Test Descrption contains essential test information and having them visible on this screen would help to understand the context of the steps without need to click multiple times to see it. Hoovering in upper right corner shows that, however it is unreadable in some cases.

    3 votes
    How important is this to you?
  2. I would like to be able to see (and report on) the issue titles and the issue ID number, for issues that are linked to tests (this is especially important for projects that do not have a 2 way issue integration)
    If just the issue ID is shown, it means always having to spend time looking up what that issue is.
    It is also important to be able to export & print a list of this information and would also be useful to be able to create a filter which allows it to be shown on dashboards.

    3 votes
    1 comment  ·  Admin →
    How important is this to you?
  3. Add possibility of tag searching in whole system. Not within one project.

    3 votes
    How important is this to you?
  4. Is it possible to add the following feature to the 2 way integration with YouTrack.
    Once user add steps to requirement that was linked to YouTrack, the steps will be displayed in the YouTrack ticket as well.

    As currently exist in the JIRA 2 way integration.

    Thanks

    3 votes
    1 comment  ·  Admin →
    How important is this to you?
  5. Show Progress on how many test cases / test steps are done / still to go when running the actual test.
    right now I have to stop the test and call the parent screen to see the Progress of the current test...

    3 votes
    How important is this to you?
  6. The possibility of adding files up to 25MB, so that can include heavier movie files with testing journeys etc.

    3 votes
    How important is this to you?
  7. Most of the times while creating tests i don't always have much description and I lose my flow when i have to go to another tab to write steps. I would like to see the steps on the same page as the landing page

    3 votes
    0 comments  ·  Admin →
    How important is this to you?
  8. In a TestSet I would like to have an extra column indicating the number of times a Test has been run; occurences.
    When Test case fails, an issue is linked to it but when the issue is resolved and the Test case passes the test, there is no way to see it was failed and ran several times. With this number of occurence you would potentially see that the Test Case was failed one or several times and that issues were linked. No need to enter all the TC 1 by 1.

    3 votes
    0 comments  ·  Admin →
    How important is this to you?
  9. It would be nice if it would be possible to add an option to pull tests that have specific words within a test's steps. For example, a filter that has
    Name has this
    and
    Steps has this

    Would help grab tests that may not have been tagged completely properly.

    3 votes
    0 comments  ·  Admin →
    How important is this to you?
  10. Generally testers write multiple test cases for a user story or feature and generally we group them in folders/filters in Test Library module. The ability to add the folder/filter to task board would be a better idea to track it in the board

    3 votes
    1 comment  ·  Admin →
    How important is this to you?
  11. As an enterprise customer of practitest I would like to see a feature called "inline editing of test cases" so that I don't have to drill into a test case - leave the screen I'm on - edit the title of the test case - then reload the entire test library again to see what else I need to change.

    Nearly every competing product supports this form of rapid editing - and its a huge deal for me from a management perspective to make quick/rapid changes - especially in avoiding load times to merely go and edit a different test…

    3 votes
    0 comments  ·  Admin →
    How important is this to you?
  12. When i run a test A which uses called steps from another test B then the preconditions from B should be also visible in my test run.

    3 votes
    How important is this to you?
  13. Currently we can define only one type for a filter, so we have to create same filter for different types. It will be great if we can choose multiple type for a filter.

    3 votes
    0 comments  ·  Admin →
    How important is this to you?
  14. We use filters to separate our application by functional area. Some functional areas have specific setup and test instructions. Currently we have to list those instructions in each test or link to confluence. It would be helpful to have a Notes section at the filter level that would allow you to store text to list specific instructions , set up, etc.

    3 votes
    0 comments  ·  Admin →
    How important is this to you?
  15. When batch importing test cases via spreadsheet, Practitest does not take you to the tests you just imported, it just states whether the operation succeeded or not.

    If would be nice if the imported tests were linked to on the result page so we can immediately start work on them. At the moment I have no idea where my imported tests end up so often have to search for them manually which takes time.

    3 votes
    How important is this to you?
  16. Provide the ability to add attachments and/or links at the filter and folder level in Test Library. This way attachments that apply to all tests in that filter or folder can be stored once and not in each test. Similiar reason for URLs. It would be a place to store test instructions, data paths etc.

    3 votes
    0 comments  ·  Admin →
    How important is this to you?
  17. This is a pity that we can't see the test description + the attachments during execution.
    + the additon of a button to end the test execution . This is a strange feeling to validate the test by coming back to its description or in instances list.

    3 votes
    How important is this to you?

    Hi Benoit,

    Thanks for your feedback.

    Kindly note that you can hover over ‘Test in Test Library’ and see the test description.

    As for the button to end the test execution, our main goal was always to save tester time hence we initially did not plan to add any additional buttons to that screen.

    Having said that, would recommend to use the keyboard shortcuts, see more information here: https://www.practitest.com/help/settings/keyboard-shortcuts/

    Thanks,
    Yaniv

  18. it is very often usefull to compare testets contents to extract information like:
    - tests removed from one testset to another
    - tests added from on testset to another
    - tests seen as passed in one testset execution and failed in another testset execution (regression or test fixed)

    seems to be possible to do this through filters and excel (macro, formulas) would be useful to have it natively supported in PractiTest

    3 votes
    0 comments  ·  Admin →
    How important is this to you?
  19. Requirement description is very important for users to overview all requirement list or check duplication after importing from excel file but now user only can see requirement description by view each requirement detail.

    3 votes
    0 comments  ·  Admin →
    How important is this to you?
  20. Our automation test execution (ATE) machine can receive a remotely command and put into queue, commands from queue will be pulled out and processed, such as 'Build', 'Program', 'Run', 'Report'... but I can't find any way to trigger our ATE from Practitest server now.

    3 votes
    1 comment  ·  Admin →
    How important is this to you?
  • Don't see your idea?