AIDEN's test automation features — QA Architect and Test Advisor — retire on November 6, 2026. After that date you can no longer generate, run, or export AIDEN automated tests in Qase. Test Designer, and everything else in Qase, keeps working as it does today.
If you want to keep any test that AIDEN generated, export its code before November 6.
Why we are retiring it
When we built AIDEN, general-purpose AI clients were not yet reliable enough to write solid test automation on their own. That has changed quickly. Tools like Claude are now much better at this work, and the Qase MCP Server gives those clients direct access to your test cases, runs, and results in Qase.
More and more teams now generate and maintain automation in the AI client they already use, with Qase as the system of record behind it. We are putting our AI investment where that work now happens, instead of into a separate automation layer inside Qase.
What is retiring
Feature | What it did |
Converted manual test cases into automated tests, including the agentic "automate with AI" workflow | |
Scored your test cases for automation readiness | |
Exported AIDEN-generated tests as code (Export code and Export autotest) | |
Ran AIDEN-generated tests in the Qase cloud, from the app or from your CI/CD pipeline |
This applies to every Qase environment, including dedicated clusters.
What is not changing
Test Designer stays as it is, and we continue to invest in it.
Test cases, test runs, and results that you created outside AIDEN are not affected.
The Qase MCP Server, the API, reporters, and every integration keep working as they do today.
Your plan and price do not change. Test Designer continues to use AI credits as before.
Key dates
Date | What happens |
Until November 6, 2026 | QA Architect and Test Advisor work as normal. Export anything you want to keep. |
November 6, 2026 | Both features are switched off. AIDEN-generated tests are no longer available in Qase. |
Before November 6: exporting your tests
The test code AIDEN generated is yours to keep, but only while the feature is still on. To export a saved AI automated test, open it from the repository and use Export autotest, pick the language and framework, then click Generate. You can copy the code or download it. Exporting AI automated tests has the full steps and the list of supported frameworks.
Export each test you want to keep. After November 6 the export option is gone along with the rest of the feature.
After November 6: generating automation with your own AI client
The path most teams have already taken is to connect an AI client such as Claude, Cursor, or Codex to Qase through the Qase MCP Server. Your AI client can then read your manual test cases from Qase, write automated tests against your own codebase, and report the results back to Qase.
That gives you what QA Architect did, with two differences: the tests live in your repository from the start, and you can use the framework and conventions your team already uses.
If you would like help working out what this looks like for your team, reach out to our support team.
FAQ
Does this affect Test Designer?
No. Test Designer is not part of this change and keeps working as it does today.
Will our other test cases or results be removed?
No. Only AIDEN-generated automated tests are affected. Everything else in your workspace stays exactly as it is.
Can we keep running AIDEN tests in the Qase cloud?
Not after November 6. AI Test Cloud ran AIDEN-generated tests only, so it retires with them. Once you have exported a test, you can run it in your own pipeline and send the results to Qase with a Qase reporter.
We use a dedicated Qase cluster. Does this apply to us?
Yes. The features are switched off on November 6 in every environment, including dedicated clusters.
Does our subscription or price change?
No. AIDEN's test automation was not billed separately, so nothing changes on your plan.