603 results found
-
Inline edit fields after cloning a test (Test name & Description)
When I clone a test, the edit dialog is displayed
I always want to edit the test name and description(almost always)It's a (minor) irritation that I cannot just type in the fields directly, instead I must press the "Edit" button
1 vote -
Implement a way to avoid duplicate tests in test sets
I know the use case for adding a test more than once to a test set (for using parameters)
However what I often do is
Filter: V1.9
Add 50 test cases
Add some to a test set (not necessarily all)
Add 10 more test cases
Go to the test set to add some of these cases -- I'd like a checkbox to show ONLY tests that are NOT already in the test setOtherwise its really easy to create duplicate test instances in the test set when I just wanted to add the new ones in
7 votes -
Display item counts in filter tree
When I select a filter, I can see how many items are in it.
I would like to see in the tree view, at the end of the filter name, the same count
so I see
All (10)
V1.1 (3)
V10.9 (1)
Old (6)Etc
4 votes -
I would like the ability to @mention someone in a text field
In Apps like Outlook and MS Teams, it is useful to "Mention" a user when I need their attention
Lets say I am writing a test and need help, in a step I could say @Nick Ambrose, please check my logic here
Then the user could get notified in-product or with an email that I need help (or their attention) and get a link to the item I need help with
1 vote -
Add the ability to convert an issue to a test case
If we determine that a bug is a good test case, It would be great if we could convert that issue to a test case from the issue detailed page.
Add the ability to convert an issue to a test case so the user doesn't manually have to add a new test case.1 vote -
Adding a testset id field which can be used to filter issue reported for a particular testset and see them on dashboard
Please have a feature which enables a user to see the dashboard updated with the number of defects raised for a particular Testset. Right now it is doable through the reports. But since Dashboard is the landing page of Practitest, it will be better if we can have that feature on dashboard also. May be we can have a field for test set id which we can add it in the Issue filter to update the dashboard view.
1 vote -
Provide Notes section at filter level for documentation
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 -
Include comments in the PractiTest API
Include comments in the PractiTest API.
17 votes
Ido Tandy
responded
-
Have an option to define multiple type for a 'Filter'
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 -
Have an option to include/add test cases that aren't already part of test set.
Currently, when you want to add a test case that doesn't already exist in a test set, user has to scroll through pages to find the test case. Marking the test in red doesnt really help
It would be great to add an option to filter out test cases that are not part of the test set and add them.
4 votes -
Enhance the PractiTest Zap on Zapier.
Currently, the PT zap can only Create a requirements or Run. Creating and updating issues actions are also important when it is integrated with other tools. Enhance the current zap to include custom fields and tags.
0 votesIdo Tandy
responded
-
Make charter not a mandatory field for exploratory tests
"Name" and "Charter" in some cases can mean the same thing and in that case where it does mean the same thing Charter should not be a required field.
2 votes -
Move Cloned reference to History section
When Cloning a test, the cloned test has a reference of the test from it was cloned and it shows up in the "Attachments" section of General section. It would be nice if this reference could be moved to History section to keep the test look cleaner
2 votes -
Test case templates
Allow creation and selection of test case templates. These could have standardized titles, step names, etc. Example:
Title: "My App: <component>: <test>"
Step 1: "SETUP"
Step 5: "CLEANUP"20 votes -
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 requirement26 votes -
Preconditions from called tests should be visible during test execution
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 -
Add an ability for optional steps
Would be nice to be able to set steps within a test to "optional".
1 vote -
Integration with TestComplete and XamarinUI Test
Integration for Automation tools for Desktop and mobile applications
1 vote -
Picking up Assignee from Youtrack 2 way integration
When you change assignee in Youtrack would be nice in a future to send it to Practitest
4 votes -
Allow users to rename Transition Status.
Renaming Transition Status will save us some time in case we misspelled a status, but don't realize it until we are done completing the transition workflow.
1 vote
- Don't see your idea?