Feature Requests

Currently if within team we want to perform test plan review we need to use 3rd party system where we can comment out missing or excessive test cases for tested feature. To improve this comment section where developers and testers can add their thoughts and review comments would be helpful feature which would allow us to perform test plan review as well as keep history of changes (what need to be added, removed or changed) centralized within one tool before test plan get accepted and executed.

For our purposes we may like to have a base set of tests for our products, but have some small variations depending upon the version of the product we are testing. So being able to duplicate an existing test plan and then modifying that plan, rather than having to create a test plan from scratch again would save us time.

I've created quite a few test runs without organizing them into test plans. It would be amazing if I could create a test plan and add previously created test runs to this new plan.

I want to select more than one plan to do a test run

We would like a feature where each test case has a point associated with it and our team members can book multiple testcases until the points matches the required amount each member is given. This way our team members can each pick a test case that they are comfortable doing whilst also allowing for fair distribution of test cases.

It is required to add test case preconditions to the test results report PDF.

How can I see more filters in test runs? For Example I would like to see 'Type' option.

Current design allows Test Run automatically reflect an update made to Test Repository. This behavior can create skewed Test Run Results when we revisit old Test Run Results.

The reporting for automated executions should be more robust. Allure is an example of how this can be done - with nested steps, attachments, stack traces, variety of information to view consume and analyze.

For lengthier test cases, knowing where a given test case has failed in previous executions in terms of its failed test steps could be helpful for several reasons, including the identification of particularly sensitive areas of code regarding the introduction of regression bugs.