General

I suggest you ...

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Add the ability to select test cases from Test Library and ADD them to existing Test Sets

    We now have the ability to Create test sets from test library, but it'd be nice to have the ability to also *add* tests to *existing* test sets from the test library. Thanks!

    52 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  2. Overall, Practitest should remember and persist column widths and sorts

    There are no pages in PT that actually remember the width of columns or sorts. This makes using PT pretty annoying for people who manage or run test sets, issues, or requirements.

    45 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. add a "comment" field for each step on the "Steps" page for review.

    When reviewing tests cases, it would be useful to have a field to comment a step when a tester is reviewing someone else tests cases. This way, he can add comments without modifying the test case. In case of misunderstanding if the specification, from the reviewer, author of the test case can update the reviewer and doesn't need to rewrite the test case.

    39 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. add the ability to duplicate filters

    it would be very useful if we can duplicate the filters (instead of re creating them every time ) in case we need them in several places.

    38 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  6 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Creation of filter via the API

    We want to be able to create filters from the API
    this will allow us to group text sets created via a pipeline and better organize what tests where ran where

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  6. Make the test name fixed (frozen) when scrolling/editing test steps

    can you add the test number to the top banner of the page? or make the test name and number line "sticky" so it will stay visible when you scroll down?
    (When I have few tests open, in order to work in parallel - I have to scroll up all the time to make sure on which test I'm on.
    very annoying... and leaves too much room for errors (=unwanted editing)

    29 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  7. Github with Two-Way Integration

    Please add two-way integration with Github. Not everyone's on Atlassian products such as Jira, Bitbucket, et al.

    28 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow Bulk Edit to Edit ALL tests in a Test Set, not just 100 at a time

    If you want to do a bulk edit of a field for the tests in a test set you are limited to what you are allowed to see on the page (max 100 now). If I have a few hundred I currently have to go to each page and do a bulk edit. What is even more tedious is after I do one it resets back to 1-100 so I have to first double check I did it correctly for say 201-200, etc. This functionality is available when doing bulk edits of tests (where it asks if you would like…

    27 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    planned  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Save search as filter

    Add ability to convert a search to a filter (which can be later customized).

    24 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add the ability to view Test Steps directly from Test Sets

    Now, the only thing we can do to view Test Steps from Test Sets is by:
    1. Clicking the instance
    2. Click "Test in Test Library"

    which means we can only see steps for a particular test at a time.

    I'd suggest that you add the ability to view Test Steps directly from Test Sets, maybe by implementing display popover? Or maybe add another page that allows us to view all steps in all the tests in a certain test set. Thanks!

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  11. Make tag suggestion *not* case sensitive

    Right now, typing a word into "Tags" field will bring up tag suggestions, which is nice and useful, but it is case-sensitive at the moment.

    For example, if the tag is "Billing" and I type "bill" without uppercase on the first character, the suggestion will not come up. I have to type it with capital B for the suggestion to come up.

    22 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. Add a "description" and "comment" fields for each "Tests set&run"

    When preparing a "Test set", sometimes we need to give extra informations about the "Set" we prepare with other builders and testers.
    It would provide us the ability to share informations such as the purpose of the "set" or any extra data needed to execute the test.

    And more, having a "comment" section in each "Set" would be helpful to share informations between testers and those who build the "Set".

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →

    Hi,

    Currently there is no description system field for “Set”, but you can create a custom field of type “Memo” for “Test Set” and use it for description and comments.

    Regardless we will review the possibility to add such a system field in the future.

    Best regards,
    Christine

  13. Allow automated test runs to be passed manually

    Currently, if a test is marked as an automated test ("Automated" checkbox is checked on the test case) the status of the test run cannot be changed manually. At times a test will fail due to an issue with the automation script itself, so we get a false fail. At that point we will run the test manually, but then we are not able to fix the status in Practitest.

    21 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Ability to add a test case to a test set by writing the test number/range

    As mentioned with the Ability to add a test case item, we tried filters; it’s cumbersome to have to shift gears and create a new filter every time that we want to look up / search for something new. It clutters things up as then there is the maintenance and scrolling to contend with as well.

    20 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  15. Make direct paste of screenshots possible.

    Very often when we are executing a test we would like to attach a screenshot. In many test tools it’s possible just to copy and paste from a sniping tool, but in practitest it seems to be necessary to save the screenshot as a file and then upload this file. This is pretty cumbersome. I suggest that you implement such a feature.

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  16. Import Jira requirement ticket with all it's sub-tickets

    In order to provide better coverage of the specifications I do propose to implement:

    - Tree-like import that means importing parent and subtickets;
    - Provide straight dependence between subticket and linked test, i.e. if Practitest user link test to subticket the test should also be linked to parent ticket automatically, as subticket is a must part of parent;
    - Add system field "Traceability" for requirements that will reflect clickable test IDs;

    If the solution will be implemented it will simplify test covering process and test covering tracking process;

    19 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Allow report generation by test set ID

    There is currently no API to generate report by test set ID. Generate report by test set ID would greatly enhance our automation process

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add requirement link to an issue when posted to Jira

    When an issue is created from a test, the associated requirements could be linked (if Jira requirements, then the Jira requirement link) to the issue document (perhaps appended to description, or to a field defined in Practitest by the user) before being sent to Jira.
    Why? So in Jira a developer can click straight on the requirement to see what should happen, rather than dig through a number of screens to access the requirement

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  19. Create filters with OR statements that span item types

    Currently it appears that filters can only be created using OR statements that meet the same item type which can reduce the ability to find what you're looking for when your test library gets to be particularly large.

    For example I can create a filter that says:
    (Name is this or that) and tag is this

    And cannot make a filter with:
    Name is this or tag is this

    Or advancing even further to:
    (Name is this and tag is this) or (name is that and tag is that)

    It would be nice to be able to have this grouping…

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  20. make requirements links visible when executing a test

    When executing a test case one of the key things you'll want to reference are the requirements, so logically they should be accessible.

    17 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 18 19
  • Don't see your idea?

General

Feedback and Knowledge Base