Feature Requests

Currently, Qase allows adding parameters to test cases, but all parameter sets share the same expected result. In practice, different parameter combinations often imply different flows and behaviors of the product under test We would like to request a feature that allows: Branching a test case based on parameter values Defining distinct expected results for each parameter set, or for specific steps depending on the parameters This would: Eliminate the need to duplicate similar test cases Provide clearer documentation of variations in product behavior Better reflect real-world testing scenarios where one test case naturally branches into multiple outcomes

Would be nice to have a Multi-URL field for custom fields similarly to the "select list (multi)" feature but without a pre-set list to select from. Basically I'm looking for a plus button to add another url link under a field instead of having to do it with a paragraph

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.

Currently when viewing results of a test run, each row is hard coded with columns for ID, MEMBER, STATUS and TITLE. It would be helpful to allow for optional columns from the test case fields to add into the results row, such as the description field of a test case. Also, adjustable column width would be helpful for being able to show more text in a column. This would allow for quicker parsing of test cases information in a test run without having to manually click on individual test cases for information beyond the default columns shown in each row.

I want to be able to annotate a test in Python, such as @qase.requirement("REQ-2") and it mark that requirement with the test case I am writing in Python.

In the test case repository >> view mode of test cases, to move to the next or previous test case, the user has to close the current test case window and open another one. If back and forward navigation controls/icons are provided, it will be easier for the user to navigate between test cases and will reduce the manual actions required.

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.

In case reviews it's not clear where an adjustment is made. Solution: Highlight the step with the adjustment.

I would like to get all requirements for a project like this client request does: https://app.qase.io/v1/requirement/tree , and a way to get individual requirements

Feature requirement with the support Link/unlink test cases directly to userstories and tickets Use versioning, preferably a way to sync milestones and iterations with Gitlab and Qase Easily see the status of test cases for every requirement Track changes to requirements in tickets so that we can determine if your test cases require updating