Release notes··4 updates
4 updates shipped on July 15, 2026.
Highlight
Featured this release
Admins can now require MFA for every member under Settings → Authentication.
Turn on "Enforce MFA" and members without a verified factor are walked through TOTP enrollment before they can use the app. Admins and owners can toggle it; members see it disabled with an explanation.
Highlight
Featured this release
GET /v1/test-cases and the CLI can now include full step definitions, and new API and MCP tools let you read and edit test cases directly.
Add ?includeSteps=true to GET /v1/test-cases (or --include-steps on qatech test-cases) to get each test case's instructions, expected results and shortnames – handy for a one-time export into another tool.
New get_test_case and update_test_case endpoints, and matching MCP tools, return a test case's full config – goal, steps, dependencies, labels – and let you patch fields like startUrlPath or RESUME_FROM / WAIT_FOR dependencies without touching the dashboard. Full reference in the API docs.
Highlight
Featured this release
Knowledge base entries and chat, agent and PR-review rules, previously dashboard-only, are now full CRUD via the public API and MCP.
New /v1/knowledge and /v1/rules endpoints – plus matching MCP tools – let API keys and agents list, create, update and delete text, link and memory knowledge items, and chat, agent and PR-review rules. Agent-rule targeting by application, label, scenario or URL path is fully addressable from the API.
Reference in the API docs.
Update 04 of 04
Ask the chat agent to export results as Markdown, JSON or CSV and get a one-click download card.
Say something like "export my test cases as a CSV file" and the chat agent assembles the file and drops a download card into the conversation – no more copy-pasting long tables out of chat.
QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.