Feature Requests

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.

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 would like the ability to export a report of all the test runs from a specific milestone. For example, export a pdf of all test runs attached to Sprint 1.

When importing in JSON file format, it recreates the suite each time, but if there is an existing matching suite, the test cases should be added under it.

We're using parameters as a way to store input values that testers need to use. I guess it would be really helpful for the tester to know exactly which step to use the parameter value. It's possible to do this with the testing in Azure DevOps...you can @ mention a paramter value in a step and the tester with be shown the appropriate value.

We’ve added a Custom Field to our test cases in QASE and are actively using it. However, we noticed that this field is not available as a filter option when creating visualizations or charts in the dashboard. Being able to use custom fields as filter criteria on the dashboard would significantly improve our ability to group, analyze, and visualize test data in a more meaningful way. Could you please let us know if this feature is on your roadmap or if it’s something that could be supported in the near future?

Implement case assignment stories in the test run of changes to the test run so that it is possible to roll back.

This is the conversation with support. TLDR; if you decide to save multiple steps after the fact under one big mega step, that is currently not possible, per support. I have this test case with 9 steps. I DON'T want to save each step individually. I'd like to select them all and save them as a single shared step for later use. Andrew • 9m ago Andrew • 9m ago saving each step individually is cumbersome and inefficient Andrew • 9m ago so I'd like to select them all so can do a batch job of saving them to a shared step Andrew • 8m ago Oh, I got it. Apologies for not catching that! Unfortunately, this is not possible currently. More than one step cannot be converted into a single shared step. Manju • 7m ago So I have to know before hand I want to create a shared step with MULTIPLE steps beforehand? Andrew • 7m ago With the current limitations, I'm afraid the shared step will have to be created beforehand, you're right! Manju • 6m ago well, I'd find this a severe limitation in someone's efficiency. Please add my request to possibly push this up as a feature request to the backlog of feature requests. Andrew • 3m ago I can do this easily in Excel or Google sheet easily so not sure how Qase shouldn't prioritize this higher. Thanks for your consideration.

Integrate the rest-assured-allure library to automatically log API request and response details in Qase, improving test traceability without manual attachments.

Add the ability to pass parameters from Qase when starting a pipeline.