606 results found
-
Add a way to trigger run machine to start a test set
Our automation test execution (ATE) machine can receive a remotely command and put into queue, commands from queue will be pulled out and processed, such as 'Build', 'Program', 'Run', 'Report'... but I can't find any way to trigger our ATE from Practitest server now.
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 -
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 votesAdminYaniv (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 -
Add parctitest "test id" from Jira (directly)when I created new ticket
Add parctitest "test id" from Jira (directly)when I created new ticket
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 -
Drop images or docuemnts in description
Hello,
Attachements are quite painful to add: this is click-click-click ... We should be able to add images or documents in the description. Images would appear in the description, so we wouldn't have to re-click to see it real sized.Additionnaly we don't understand why we can't see the description of the test while executing test cases . Is it intentionnal ? Thanks !
7 votesThe option to drag & drop files into the description will be supported in the new forms UI we are working on these days. The test set / Issues form already have this option - soon all items will have it as well
-
Ability to customize time for scheduling reports in practitest.
Currently practitest tools schedules all report (daily / weekly or monthly) at 6.00 AM but it would be great if tool allows to customize time for scheduling the reports to be delivered.
4 votesIdo Tandy responded
-
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 -
Search bar improvement
Hello,
Search bar has limited capabilities for now. It would be great to be able to be less limited, mainly to be able to search for numbers.Furthermore we could avoid the need for ** or "" .
Thanks !
1 vote -
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 -
Attach files on bug report
To be possible to attach files at the time the bug is reported to Jira.
1 vote -
Versioning test cases
Feature to versioning of test cases, allowing comparisons of differences and return to previous versions.
69 votes -
1 vote
-
1 vote
-
1 vote
-
1 vote
-
1 vote
- Don't see your idea?