There's a specific kind of exhaustion that comes from knowing exactly what needs to be done, but the tools won't let you do it efficiently. You've got the vision—automated test coverage across three projects, a clean migration path, tests that actually reflect production—but between you and that vision sits a thousand small frictions.
Q4 was about eliminating them by paying attention to the places where your workflow stutters. The moments where you think "there has to be a better way" and then resign yourself to the manual approach because, well, that's just how it works.
Except now it doesn't have to.
The Automation Backlog Problem (And How We Actually Are Solving It)
Eliminating "Automation Paralysis"
Let's talk about the elephant in the repository: your mountain of manual test cases that should be automated but aren't. Not because you don't value automation(you do), but because the conversion process is soul-crushing. One test at a time. Selectors. Wait times. Edge cases.
So the backlog grows. And every sprint planning meeting, someone mentions it. And everyone nods. And nothing happens.
AI-Powered Bulk Conversion changes the entire dynamic. Select a batch of manual tests and click 'Automate.' AIDEN runs a pre-flight check, flags the cases that need human attention (vague preconditions, overly complex flows), and converts while you grab coffee.
A UI Built for How You Work
We rebuilt the entire AIDEN interface with a full-screen modal and unified flow whether you're converting or generating from scratch. Environment setup is baked into the process.
The JSON editor? Gone. AIDEN's stability reached the point where the safety net became unnecessary clutter.
You can now add steps on the fly, edit as you go, and export code from a dedicated tab in the right panel.
API Testing Because Your App Isn't Just a UI
Here's something we heard a lot: "What about my API layer?" Fair question. AIDEN now generates autotests that validate APIs.
Pre-warmed Environments for Speed
We’ve re-engineered the backend of AIDEN so browser environments are ready the second you hit "Automate." No loading spinners.
Real-World Automation
The 70% Truth: Most vendors will tell you their AI achieves 95% automation rates in a perfectly curated lab. We’d rather tell you the truth. Based on real-world usage in messy, edge-case-riddled production environments, AIDEN is now automating over 70% of manual boilerplate.
That might not look as "sexy" on a marketing slide, but think about the math: if your team spends 40 hours a week on manual regression, you just got 24 hours back. Every week. To make sure you actually use that time, we’ve doubled AIDEN credits across all plans and implemented hard expenditure caps, so you can scale without "Cloud Bill Heart Attacks."
Qase is Now "AI-Native" with MCP
We know that for many of you, AI is becoming the "connective tissue" of your entire engineering stack.
This quarter, we launched the Qase MCP Server. The Model Context Protocol (MCP) is a new open standard that allows AI models to safely interact with your data. By plugging Qase into your local AI assistant (like Claude Desktop), you can now ask high-level questions about your quality state without leaving your workspace.
AIDEN remains your expert for building and running tests, but the MCP server makes Qase a Knowledge Base for your entire engineering workflow.
Architecture That Scales With You
Shared Steps Go Global: Quick question: How many times have you copied the same "user login" shared step across different projects?
If the answer is "more than once," you've been working too hard.
Global Shared Steps live at the workspace level now. Build your authentication flows, payment scenarios, and teardown sequences once. Use them everywhere. Update in one place, deploy to infinity.
- Linked Shared Steps: Refactoring used to come with anxiety. Which tests use this? What will break if I change it? Now, when viewing a Shared Step, you instantly see all associated test cases. One click shows you the complete impact zone.
The Most Requested Features
- The Failed-Test Clone: Our user feedback board had one feature request that kept climbing: "Let me rerun just the failed and skipped tests." Close a test run with failed/skipped tests only, clone it with just those cases, and retest without wading through hundreds of passing tests.
- Clone Wars Sequel: Ever noticed how you avoid starting new test cycles because recreating the structure feels harder than it actually is? Test Plan cloning removes this worry entirely. Last sprint's plan becomes this sprint's foundation in three clicks. Keep the assignees or don't. Rename it inline. Done.
The activation energy to start drops to near-zero, so you start. Momentum builds from there.
- Webhooks: You can now push test results via Webhooks to third-party tools. This unblocked several enterprise customers who needed test data consolidated into platforms like Aha!.
It's the kind of integration that sounds mundane until you realize it's the glue holding your entire quality ops together.
- Data Retention: The Auditor Insurance Policy: Our default data retention works for most teams. But regulated industries, mature enterprises, and anyone who's ever heard the phrase "we need historical data for the compliance review"—they need more. The Data Retention Add-on extends test result history to 5 or 10 years. Transparent pricing, prorated per user.
The Invisible Infrastructure Improvements
Some updates don't make headlines but change everything about how the platform feels:
- Async downloads means exporting 10,000 test cases doesn't turn into a staring contest with a progress bar.
- Full suite paths in QQL solved the "which Regression Tests suite are we talking about?" problem that plagued every large repository.
- Include children suites means querying a parent now returns everything nested beneath it. No more manual enumeration of every child suite.
- We also patched 20+ security vulnerabilities in our JS reporters, added Vitest support, updated Mocha to version 11, improved Cypress/Cucumber integration, and shipped quality-of-life fixes for Robot Framework, Pytest, and Playwright.
None of these will change your life individually. Collectively? They're the difference between a tool that fights you and a tool that flows.
What This Actually Means
Software releases usually follow a pattern: big promises, modest delivery, PR spin to bridge the gap.
We're not interested in that game.
Everything in this post is live. In production. Available now. The bulk conversion that eliminates your backlog anxiety? Shipped. The AIDEN UI that gives you room to work? Deployed. The global shared steps that scale across your workspace? Running right now.
QA is evolving from "the people who find bugs" to "the people who design quality systems." Q4 was about giving you the steering wheel for those systems.
We're not asking you to imagine what testing could be like. We're showing you what it is.
Happy testing.
Don't miss out on future updates and valuable content! Connect with us on LinkedIn to stay informed about all things Qase.
