Skip to content

General

General

Categories

544 results found

  1. Current ly Excution Progress chart only support fillter of project with less than 10 000 instance (total instance of whole project).

    4 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. ability to add issue: fields to an instance report.

    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)
  3. I need to create a filter to collect all test result older than 4 days. Tried to filter with Last Run field but I can't see suitable operator. It must be good if we can use today() instead of select specific date on calendar or there is operator such as: Before the last X days...

    6 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)
  4. If you have a custom field that uses the user list; only current users on a project are available. If that field needs to be set after the user has been removed from project, they are no longer available as a selection item.

    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)
  5. Allow addition of new items to a linked list child list from the form drop down. This feature was added to regular lists a while ago and is much more convenient then modifying the list contents in the fields settings section.

    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. I would like to have the option to batch delete all the tests within multiple TestSets. Alternatively, if I clone multiple TestSets, I should have the option to delete the tests within the new cloned TestSets

    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)
  7. In a context of automated test, it could be valuable to be able to append new values to fields already existent via API.

    At the moment, we can only replace the entire Field with new possible values. And if something goes wrong, I feel like there's a high chance to lose information.

    17 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)
  8. I am looking for an easy way to report on the status history of an issue. As it is now, I can only easily filter on current status when I create reports/filters. I am looking for a way to find issues that were ever in rejected status or were at one time set to "reopened" without having to manually read the history of every issue.

    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)
  9. When creating a bug using JIRA integration currently all steps in the test are pased into the jira description. It would make more sense to only paste the step that failed and the results from that step. this would give the user the information on the actual issue and reduce the amount of editing currently required using jira integration

    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. I would be interested by having a way to group different values of a field used to create a pie chart in 1 "super value"
    To give an example:
    For the Requirement items, I would like to have a pie with only 2 values :
    - Not Covered
    - Covered
    As of today, we have: Not Covered, No Run, Passed, Failed...
    I would like to be able to present a dashboard to my manager with the value "Covered" including all the values except Not Covered and Not Covered.

    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)
  11. Creating a daily report to see what test cases have been changed, so that we can keep our testsets up to date with the new changes in the library.

    adding what changed as a report option would simplify the work flow of opening up Project History

    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)
  12. We would love the ability to run cURL commands form within Practitest so that we can launch our automation from within a test run.

    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)
  13. PractiTest supports a synchronization with YouTrack, especially for the bug creation (from PractiTest to YouTrack).

    There is currently no way to change the call on PractiTest test side.
    YouTrack proposes a feature to update object on Event, such as issue creation.
    I would need to identify that the issue is coming from PractiTest, and then I would be able to make my change on YouTrack side.

    The signature includes 2 fields, which are not filled today: externalId and externalUrl, which shall be filled in my opinion when the issue is created from an external tool.

    Could you please fill at…

    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)
  14. Currently, test modification email notification does not inform the Test admin about the exact changes done at step description and step expected result. This is must needed request . Even Project history does not keep the record of test modification at the level of Steps description and Step expected result

    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)
  15. When creating a manual parameterised test set, multiple instances of a test case need to be added. At present this needs to be done individually. It is suggested that there is an option to 'Add multiple instances' to the dropdown menu by the '+ Add selected tests' (underneath Add all test in view). This triggers an input box to appear where a two digit number can be entered, and all test cases ticked will be added that number of times

    16 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  2 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. When adding in the parameters there is a checkbox that is unpopulated by default. To enter a value in the parameter field, this needs to be checked.
    Although in isolation it is a small thing to have to click the checkbox each time, it soon builds to a significant irritation when preparing multiple test cases

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  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. This will make this process more productive and easy.

    Same as you do in JIRA tickets - pasting a screenshot from clipboard within the create screen, automatically uploads it to the ticket.

    10 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. When we create custom fields or modify a System field, it would be great to add a Description that we could then view as a tool tip in the entity. This would give more context around the importance or purpose of the field and would give testers a more compelling reason for filling it in.

    Right now, we document the purpose and description of each of the fields and filters we have set up in a wiki page. It would be nice to be able to manage this directly from PractiTest.

    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)
  19. Hello, Can we request to remove text " PractiTest: Linked Results (Runs)" from the view of the main screen and omit from issue type which are not integrated in setting of the project ? We just want to see it on the right pane which is ok

    Is there any possibility to add this feature?

    Thanks,
    Faisal

    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)
  20. While creation of an issue via API, I would like to link it to a test case which failed.

    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?