580 results found
-
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 -
In The Task Board As Well As Filtering by Person why not filter by TestSet Filter & Test Filter -
That way you can multi purpose it for multiple test runs.
15 votes -
Allow creating a test set based on requirements
Allow creating a test set based on the tests linked to one or more requirements. Example:
- search for all requirements with tag 'ABC'
- select all or some of the requirements
- click the 'Create Test Set' button/link above the resultsAll the tests linked to each checked requirement is put into the test set.
5 votes -
PractiTest integration with Clubhouse
Have a 2 way integration with Clubhouse
5 votes -
Enable Esc or blur() collapse of dialogs
Some dialogs require a specific click to close. Examples: [Info] for any test in the Test Library, [show requirements] for any test's Traceability tab. These should get dismissed with the Esc key, and when clicking outside of the dialog.
1 vote -
Implement a step library, and/or allow "call to test" subsets
We have many steps that are reused all over the place, but not necessarily in the same order. We also have step sequences that, on their own, do not constitute complete tests. So we now have tests that exist only as step sources for other tests, sometimes with a single step each.
It would make more sense, as a user, to have a library of individual steps and step sequences that can be referenced without having to create tests just for this purpose.
Another way to do this would be to allow "call to test", or something like it, to…4 votes -
Allow parameters to pull values from custom fields or value lists
Parameters and permutations are great, but frustratingly separate. It would be good to allow parameters to use values defined in a list for a custom field, or a new artifact for this purpose. Maybe they could also be passed inline with the parameter instantiation:
{{myParam:[1,2,4,8]}}6 votes -
Provide the ability to set default values for parameters
When creating a parameter, it would be great to be able to set a default value. This could be done similar to a python, with the equals sign: {{myParam=4}}.
1 vote -
Create API endpoint for deleting users
Create API endpoint for deleting users
1 vote -
Make the "Add requirements..." field case insensitive
In the test Traceability tab, the requirements field ("Add Requirements by typing their ID's") is case sensitive. This is annoying, especially since the failure does not say anything about capitalization. All requirements are upper case, so capitalization can be assumed.
1 vote -
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.
33 votes -
Enhance UI CSS with Dark Mode / Compact Test Steps Listing
As an enterprise customer I would like to have a "Dark mode" feature set as my personal preference, as well as see compact test steps listings, so that I can enjoy spending time working in Practitest.
9 votes -
Support inline-editing of test cases
As an enterprise customer of practitest I would like to see a feature called "inline editing of test cases" so that I don't have to drill into a test case - leave the screen I'm on - edit the title of the test case - then reload the entire test library again to see what else I need to change.
Nearly every competing product supports this form of rapid editing - and its a huge deal for me from a management perspective to make quick/rapid changes - especially in avoiding load times to merely go and edit a different test…
3 votes
- Don't see your idea?