613 results found
-
Github with Two-Way Integration
Please add two-way integration with Github. Not everyone's on Atlassian products such as Jira, Bitbucket, et al.
40 votes -
Clone Test Set with current test status
There should be an option to allow the user to clone either as anew Test Set or with existing Test Status.
It will help us to run the same test set with multiple versions of our product.
Currently cloning reset all the test statuses.
3 votes -
Show Requirement Description field
Requirement description is very important for users to overview all requirement list or check duplication after importing from excel file but now user only can see requirement description by view each requirement detail.
3 votes -
PractiTest integration with Clubhouse
Have a 2 way integration with Clubhouse
5 votes -
Give option to only run tests on instances that have 'ready' status within test set
At the moment, when I've created a new test I will leave it as 'draft' status until the feature comes available for me to test. However, I like to have my test sets organised and ready to go. It would be useful to have an option to only test the instances within a test set that have 'ready' status. This would save accidentally initiating tests for the instances that are not yet ready and are still in draft.
2 votes -
Add the possibility to compare two/several testsets contents
it is very often usefull to compare testets contents to extract information like:
- tests removed from one testset to another
- tests added from on testset to another
- tests seen as passed in one testset execution and failed in another testset execution (regression or test fixed)seems to be possible to do this through filters and excel (macro, formulas) would be useful to have it natively supported in PractiTest
3 votes -
Add Task board / Kaban keep last set filter
Each time the Task board (Kaban) screen opens the default filter is set.
Request to keep the last set filter.1 vote -
test execution
This is a pity that we can't see the test description + the attachments during execution.
+ the additon of a button to end the test execution . This is a strange feeling to validate the test by coming back to its description or in instances list.3 votes
AdminYaniv
(Product Manager, PractiTest)
responded
Hi Benoit,
Thanks for your feedback.
Kindly note that you can hover over ‘Test in Test Library’ and see the test description.
As for the button to end the test execution, our main goal was always to save tester time hence we initially did not plan to add any additional buttons to that screen.
Having said that, would recommend to use the keyboard shortcuts, see more information here: https://www.practitest.com/help/settings/keyboard-shortcuts/
Thanks,
Yaniv -
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 -
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 -
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 -
In Test Library provide the ability to add attachments to a filter or folder
Provide the ability to add attachments and/or links at the filter and folder level in Test Library. This way attachments that apply to all tests in that filter or folder can be stored once and not in each test. Similiar reason for URLs. It would be a place to store test instructions, data paths etc.
3 votes -
Provide a link to tests after they've been imported
When batch importing test cases via spreadsheet, Practitest does not take you to the tests you just imported, it just states whether the operation succeeded or not.
If would be nice if the imported tests were linked to on the result page so we can immediately start work on them. At the moment I have no idea where my imported tests end up so often have to search for them manually which takes time.
3 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 -
Mantis 2-way integration
For now Mantis is a 1-way integration. Which means that once a test failed, the bug is created in Mantis.
The problems are :
1- we have to manually re-link the bug in Practitest
2- No info appear in the Report unless we re-recreate the bug in the Issue part.Having these 2 features would be a great improvement.
Thanks !1 vote -
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 -
9 votes
Ido Tandy
responded
-
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 -
Attach files on bug report
To be possible to attach files at the time the bug is reported to Jira.
1 vote -
1 vote
- Don't see your idea?