AIDEN's test automation features — QA Architect and Test Advisor — retired on November 6, 2026. You can no longer generate, run, or export AIDEN automated tests in Qase. Test Designer, and everything else in Qase, keeps working as it did before.
Why we retired 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 retired
Feature | What it did |
QA Architect | Converted manual test cases into automated tests, including the agentic "automate with AI" workflow |
Test Advisor | Scored your test cases for automation readiness |
Code export | Exported AIDEN-generated tests as code (Export code and Export autotest) |
AI Test Cloud | Ran AIDEN-generated tests in the Qase cloud, from the app or from your CI/CD pipeline |
Authorization profiles | Stored the login credentials AI Test Cloud used to sign in to your application |
This applies to every Qase environment, including dedicated clusters.
What did not change
Test Designer stays as it is, and we continue to invest in it.
Environments stay. Only the authorization profiles linked to them retired.
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 before.
Your plan and price do not change. Test Designer continues to use AI credits as before.
Generating automation with your own AI client
The path most teams have 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 before.
Were our other test cases or results removed?
No. Only AIDEN-generated automated tests are affected. Everything else in your workspace stays exactly as it was.
Can we still export the tests AIDEN generated?
No. Export retired with the rest of the feature on November 6. If you exported a test before then, you can run it in your own pipeline and send the results to Qase with a Qase reporter.
Can we keep running AIDEN tests in the Qase cloud?
No. AI Test Cloud ran AIDEN-generated tests only, so it retired with them.
We use a dedicated Qase cluster. Does this apply to us?
Yes. The features were 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.