January is usually the month of resolutions. In the software world, that often translates to lofty roadmaps and promises of what’s coming eventually.
But in engineering, we don't live in "eventually." We live in the current sprint. We live in the reality of the release cycle where the only thing that matters is shipped code. So for our first update of 2026, we didn't want to just promise the future. We wanted to ship it.
This month, we focused on the way you interact with your software quality. We’re moving from a world where you have to micromanage every click and selector to one where you simply state your intent.
Here is how we are setting the pace for the rest of the year.
Pillar 1: Intent-Based Engineering
Agentic Mode is Here.
We teased this back in 2025, and today it’s live.
For years, end-to-end testing has been a translation problem. You know what the feature is supposed to do ("Allow a user to buy shoes"), but you spend hours translating that intent into selectors, wait times, and boilerplate code. It’s a context switch that pulls you out of the creative work of building.
With AIDEN Agentic Mode, we are removing the translation layer.
You simply tell AIDEN your goal, "Verify I can purchase shoes on our marketplace," and it figures out the path. It builds the test for you.
AIDEN breaks your natural language instructions into actionable steps, provides visual feedback (screenshots) for every action, and generates the code in your preferred language. You can give simple commands, or you can get specific with compound instructions.
For example, instead of manually scripting input fields, you can just tell AIDEN: "Click on 'Get a Demo' and fill the email address as '[email protected]'." AIDEN understands the context, finds the email field, and executes the specific input exactly as requested.
But we didn't stop at the UI.
API Testing and Random Data
Modern applications aren't just front-ends. AIDEN can now execute GET and POST API requests directly within your flow using CURL commands. This allows you to mix UI interactions with backend validations in a single, fluid test.
And to ensure your pre-production environment doesn't get clogged with duplicate data, we’ve added a Random Data Generator. Stop hardcoding static users. AIDEN can now generate unique usernames, emails, and passwords on the fly. Whether you are converting a manual test or building from scratch, just mark a field as "random," and we handle the entropy.
The real automation!
Pillar 2: Reliability in the "Untestable"
Self-Healing and Canvas Support.
There are two things that keep engineering teams up at night: flaky pipelines and black-box UIs. We tackled both this month.
Self-Correcting Tests
The most frustrating part of test generation is when AIDEN attempts to create a test but makes incorrect assumptions about the steps needed. AIDEN is now capable of self-correction during test generation. When a test fails to generate properly, AIDEN analyzes what went wrong, adjusts its approach, and re-attempts the generation with a corrected strategy. This means fewer failed test generations and more reliable test creation on the first try.
While full self-healing—where tests automatically update when your codebase changes—is on our roadmap, this self-correcting capability during generation is a significant step toward that goal. It keeps your test creation process smooth and reduces the manual intervention needed when working with dynamic applications.
Conquering the Canvas
Historically, tools like Miro, Figma, or any heavy <canvas> based applications were automation dead zones. Standard frameworks struggle to "see" inside those elements. AIDEN now supports Canvas-based UIs. It interprets visual elements within the canvas just like standard DOM elements, opening up a massive new frontier for test coverage for teams building complex, visual tools.
Pillar 3: Visualizing Your Velocity
Data is only useful if your brain can process it.
We noticed that many of you were running complex QQL (Qase Query Language) queries, then staring at rows of tabular data trying to spot trends. That creates cognitive friction when you're trying to make quick decisions about release health.
We’ve introduced QQL Bar Charts.
You can now instantly toggle your query results from a table view to a Bar Chart visualization. Want to see test case distribution by project? Or flaky tests grouped by status?
- SELECT (project, COUNT(*)) GROUP BY project
- SELECT (status, COUNT(*)) isFlaky = true GROUP BY status
Save these views to your dashboard. Spot the bottleneck in seconds.
Pillar 4: Repository Hygiene at Scale
Clean Code, Clean Tests.
As your product grows, "technical debt" isn't just in your codebase. It lives in your test repository too. Thousands of duplicate steps scattered across projects slow everyone down.
We’ve overhauled how you manage Shared Steps to make spring cleaning easier:
- Bulk Conversion: Select multiple local steps and promote them to Global Shared Steps in one click. Note that this puts them at the workspace level, making them accessible to your whole organization.
- Bulk Delete with Safety: Need to deprecate old logic? You can now bulk delete shared steps with options to either cascade the delete (be careful!) or convert them back to local steps within the test cases so you don't break history.
Enhanced Test Framework Support
Your test automation ecosystem is only as strong as the integrations that connect it. This month, we expanded our reporter coverage to meet you wherever you are in your testing stack:
We've added NUnit and Junit4 reporters for Android tests, giving mobile teams the same seamless reporting experience as web teams. The Behave reporter now supports attachments for steps, so your BDD scenarios can include screenshots and logs exactly where they matter. CucumberJS users can now leverage parameters and suite annotations for better test organization. And for JavaScript testing frameworks—Mocha, Vitest, and Jest—we've implemented support for expected results and input data at the step level, making test reports more informative and actionable.
Jira Data Center 10.x Support
Seamless integration isn't a luxury. It is a requirement. We are officially supporting Jira Data Center 10.x. Whether you are on the cutting edge of Jira versions or maintaining a stable enterprise environment, your data flows seamlessly between Qase and Jira.
Our New Feedback Tool
We moved our feedback and roadmap to a new tool at roadmap.qase.io. You can submit feature requests, vote on what you want to see next, and track what we're working on like you used to. We will continue to make sure that your requests are taken good care of.
If you used our old feedback platform, you can migrate your data. Sign in with your email to claim your posts.
We removed the barriers in January. Whether that is the barrier between natural language and code, or the barrier of "untestable" canvas elements.
We’re excited to see what you build when you don't have to sweat the small stuff.
Happy testing!
