Skip to content

General

General

Categories

566 results found

  1. When running testset, some of steps may be blocked\failed\skipped. it will be helpful if you could hide passed steps and see only who need a second review.

    1 vote
    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. As a practitest user, I want to clone my test cases and attributes, specifically folder location.

    Acceptance Criteria:
    If the folder structure does not exist, create the folder directory (a unix example would be mkdir -p /root/parent/leaf where if only /root exists, the rest of the directory is created.
    Provide an option not to create and place in the folder structure

    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)
  3. Currently filter Types supported: Issue, Test, TestSet, Requirement. Can you also please add 'Instance' to the filter type support. We include quite a few custom fields on our instances and it would be nice to create a filter using these custom fields for all the instances.

    14 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)
  4. We think the following would improve the Jira integration tremendously if implemented:
    - In the auto generated issue description (when clicking fail & issue) include the expected result

    • Make linking existing issues less cumbersome. At the moment users need to:
      1) Add the ID
      2) Navigate to the issue
      3) Edit it with the pt_id
      4) refresh in the step
      This should all ideally done by PT (itself + the Jira plugin)

    • Full 2 way integration: add a tab in Jira that lists hyperlinks of all the linked PT tests (other tools such as QMetry do this)

    6 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)
  5. By making Step Expected Results a Pass/Fail checklist so a user can check off the results as they go.

    It would also be nice if these Expected Results are stored in a library for use in future test steps as well.

    This increases test accuracy and allows for a more efficient management of expected results. Also, in the event of a bug, you can automatically report exactly which expected result was not met.

    This will greatly reduce time and energy spent by the development team trying to figure out exactly what failed to occur.

    3 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)
  6. Would like to have a single dashboard that can cover multiple projects. As a manager of projects this would be highly benefitcial.

    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)
  7. When using the Redmine 2-way integration, currently users need to go back to Redmine in order to see the bug list or in order to edit the bugs.

    It would be very helpful if Practitest users would be able to view and edit the bugs from the "Issues" tab or even view them on the different dashboard widgets.

    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)
  8. In case an issue related to test we will see a "green bug" indication.
    I think for better test planning you should provide different indication for open/fixed/close issues so I will now if to run this test and its priority.

    Generally better correlation between Issues and test sets is needed.

    2 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)
  9. 1 vote
    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)
  10. Allow the cut and paste of information from Word, Excel or any othe non-8 bit editior.

    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)
  11. We use parents in our requirements so from Requirements I always view as a Tree. When I am in a test case and click the Traceability tab to link to a requirement and I use "Show Requirements" it only shows me a flat list in ID order so I have to maintain an XLS cheat sheet to add so I can see in tree view. It would be a GREAT enhancement to PractiTest to be able to choose Tree View from the Test Case Traceability tab on Show Requirements and save me a ton of time. Thanks :)

    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)
  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…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  13. Say you have a mandatory field named 'Feature' in test cases. You might want to create a view named Features according to the value the Feature field has.
    Currently you have to specify a view for each value of Feature.
    Moreover, if you have a new feature, you have to add it manually to the filter.

    0 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)
  14. Currently, linked lists only support standard lists as the child item. There should be an option to add both lists types as the child of a linked list.

    5 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)
  15. (1) link test cases to externally stored requirements (In fogbugz) and push the externally stored requirement data into Practitest requirements for reporting/dashboard.
    (2) Add a Push link next to the Defects field in the Test Run Result screen which pushes a bug report to the external system (FogBugz) without leaving Practitest and make a copy in 'Issues' at the same time for reporting/dashboard.
    (3) Hyperlinks to externally held data if only linking to issues/requirements in the external system and not pushing data to and fro (hovering the mouse cursor over a fogbugz case ID in either issues or requirements screen…

    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)
  16. (Short report description/summary to be added manually by the reporter)

    0 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)
  17. Add ability to copy a hierarchy from one project into another.

    1 vote
    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)
  18. When there are many views (as being recommended by PractiTest) it is hard to manage them in the custom view list table.
    By filtering and/or sorting this table (by type, name, owner..) it will be easier to use

    1 vote
    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)
  19. e.g. I have created one Custom View as 'View1' which has several child custom views such as 'View1.1','View1.2'. Now i create another custom view below 'View 1' as 'View 2'. Having the ability of simply copying 'View1.1' and 'View1.2' under 'View 2' would save lot of efforts for users. Especially if you see your project having number of similar tasks being created under it repeatedly.

    10 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. Time estimation against test duration which sum at the requirements level to see how long it will take to test the entire requirement

    1 vote
    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)
  • Don't see your idea?