603 results found
-
Add a Check Box for Tests that are just Steps that are reoccuring but not needed in the TestSet
There are many cases where "Login as.." for instance is just called by other tests so that is not repeated in every Test, These "Login as" Tests are necessary but not necessary in the TestSets. Could a small check box, "Do not include in TestSet" be added so when we create a TestSet the Unnecessary tests are not visible or Color Coded to let the Tester know that Test is not needed in the TestSet? We are currently using xx as a prefix in the Test Name to distinguish these types of tests. Love your product!
3 votes -
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 -
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 -
clone a requirement
Please add a way to clone an existing requirement (to be modified later).
11 votes -
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 -
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 -
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 -
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 -
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 -
Add ability to get the steps based on filter-id.
I want to get the steps of test cases which are in Automation status (Automation filter).
3 votes -
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 votesAdminYaniv (Product Manager, PractiTest) respondedHi 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
- Don't see your idea?