General

General

Categories

  1. We would like the test history to be more detailed. Currently it only shows us what step was updated but not a comparison of the changes made. We would like to see what was changed and what it was changed to (before and after). This would be of tremendous help during an audit if anything were to come up.

    67 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. 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  ·  Flag idea as inappropriate…  ·  Admin →
  3. BDD automation has a feature call "Scenario Outline", where you can define a table data for the test. This feature is based in step parameters.
    PractiTest hosts also a step parameters feature, although the table data is defined at run time, unlike BDD automation, which is defined at test definition time
    This can be solved with a custom field hosting the table data, where automation framework can retrieve it using the API, but the problem is when we try to create a run.
    I have tried FireCracker with a Scenario Outline test and the report is not accurate because it…

    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  ·  Flag idea as inappropriate…  ·  Admin →
  4. Currently, I am using an extraction of issues and test statues to identify in Excel:
    - Failed tests linked to closed issues => for testers to update the status of the test
    - Failed tests not linked to any issue => for testers to link them to an issue
    - Highlight the issues that need to be replied to or retested (e.g. rejected, fixed)

    This involves:
    - Duplicating lines where tests are linked to several issues
    - Vlookups between issue statues and test statuses

    My idea would be to have triggers in the UI and perhaps also by email to…

    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  ·  Flag idea as inappropriate…  ·  Admin →
  5. 2 way integration into zenhub.

    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  ·  Flag idea as inappropriate…  ·  Admin →
    1. if a test in a test instance is modified, it would have been marked somehow so it would be differentiated from the original test.

    2. In addition that an option to lock "update the original test", so he won't be able to easily update the original test.

    3. Give an option to change a test for a test set for all runs, in a way that it doesn't "call" the test but clones it while giving an option to edit it.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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  ·  Flag idea as inappropriate…  ·  Admin →
  7. Step names are not required within the tool and it is an extra hassle to have to include them when we import test cases from a spreadsheet. Could you make that a non-required field when importing?

    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  ·  Flag idea as inappropriate…  ·  Admin →
  8. In the tabular with steps report it is not possible to configure which fields to add to the issues tab, for example, priority.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  9. Add a way to select a bunch of tests then batch edit them to make a single change to a bunch of tests. That way, you don't have to go into 1 (of say 1000) tests just to modify the test with ONE word. So, if my tests name is Batch Production Phone Edit and I want to change it to Batch Production Phone Edit 1, Then Batch Production Phone Edit 2 etc. etc. I can just select each test and then batch edit to add the numbers to the end of the test title.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  10. I have a requirement to enable adding tests directly in test sets. Presently, when we try to add a test instance there, it shows just 2 columns. Test ID and Title. There is no way I can add more columns and resize the window.

    That's required when we want to create different test sets as per execution type, test level or as per area/application field(custom fields).

    Only way to do that now is create different filters as per the need in test library, get the tests and add them to the instances.
    Since in my one project, I have 5-6…

    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  ·  Flag idea as inappropriate…  ·  Admin →
  11. This way we would not have to go back and edit the name of the test or the test set later.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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  ·  Flag idea as inappropriate…  ·  Admin →
  13. We often add 10 or more test cases to each requirement which means having to click "Add" that number of times to link each test case. It would be nice if there was a way to add all of them at once.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  14. For auditing purposes would be nice to be able to download the screen shots or attachments for each test.

    This way i can send to the auditors during audit season

    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  ·  Flag idea as inappropriate…  ·  Admin →
  15. We would like to have step parameters in the preconditions field as well.

    4 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 →
  16. Currently the latest updates chart for dashboards only shows the last 5 items. Being able to show more than just the 5 latest updates would be useful to provide a better insight into what is being worked on inside dashboards.

    Adding a way for users to select an amount of updates to show would be a good solution, allowing people that only want to see 5 updates to still only see 5 but allowing others to see more if they wish to.

    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  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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  ·  Flag idea as inappropriate…  ·  Admin →
  18. in the big project and data increasing, we noticed the API call limits stops developing and integrating with automation testing pipleline.

    It would be a great to run testing and updating issues if PractiTest support provision of batch API to avoiding limitation of API call (100 / 1 mins, and returned records )

    6 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. 9 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?