Qase Product Updates: February 2026

There is a breaking point in every engineering organization. It usually happens when you cross a certain threshold of test cases or team members. Suddenly, the processes that worked for a team of ten become the bottlenecks for a team of a hundred.

Scale changes everything. It turns flat lists into endless scrolling, simple queries into noisy data, and single-project reporting into a logistical nightmare.

In February, we focused on that threshold. We shipped updates designed specifically for organizations operating at scale and features that turn your test repository from a simple storage unit into a governed, architected library.

Here is how we are supporting your growth.

Pillar 1: Architecting for Scale

From "Lists" to "Asset Management."

In a startup, a shared step is a convenience. In an enterprise, it is a dependency. When you have thousands of shared steps across dozens of projects, treating them like a flat list is a liability. It creates duplication, makes maintenance impossible, and slows down onboarding.

We have fundamentally upgraded how you manage these assets with Folder Structures for Shared Steps.

This isn't just about tidying up. This is about architectural hygiene. You can now structure your shared logic by domain—Billing, Auth, Compliance—creating a navigable hierarchy that acts as a single source of truth. We’ve added bulk actions to move, clone, and rename entire directories, giving you the controls you need to refactor your test library as easily as you refactor your code.

We also introduced Child Steps in Shared Steps.

Complex systems require modular testing. You can now nest child steps directly inside shared steps, allowing you to build sophisticated, multi-layer "meta-steps." A "Checkout Flow" shared step can now contain the specific, governed logic for payment, address validation, and inventory checks nested within it. It allows for high-level reuse without sacrificing low-level granularity.

Pillar 2: Workspace Governance

Signal over Noise with Private Queries.

In a large organization, a shared workspace can quickly become a tragedy of the commons. If every engineer saves every exploratory query to the public list, the team’s critical dashboards get buried under temporary data.

We are introducing Private Queries to solve this workspace pollution.

Now, engineers can save their specific, investigative queries without broadcasting them to the entire organization. It allows for personal productivity workflows that don't degrade the shared environment. If a query proves valuable for the wider team, it can be promoted to public status but we’ve designed the flow to default to hygiene first.

Note: To ensure strict permission governance, private queries are currently restricted from shared dashboards.

Pillar 3: Data-Driven Decision Making

Executive Visualization with Donut Charts.

At the executive level, you don't need rows of data; you need immediate insight into health and distribution. We’ve added Donut Chart Mode to QQL to support high-level reporting.

You can now toggle complex datasets from tabular views to visualizations instantly. Whether you are presenting a quarterly quality review or checking the distribution of automation coverage across business units, this view allows stakeholders to understand the "shape" of the data in seconds.

Pillar 4: The Monorepo Reality

Native Support for Complex Architectures.

The modern enterprise doesn't always fit neatly into "one project, one repo." You are likely running monorepos, microservices, or complex distributed systems where a single CI pipeline touches multiple business domains.

Your tooling needs to reflect that reality.

• Multi-Project Routing (JS & Python): We have engineered our reporters to handle the complexity of enterprise codebases. Our JavaScript and Python reporters now support Multi-Project routing. If you have a monorepo that triggers tests across three different product lines, our reporters can now intelligently route those results to the correct Qase projects in a single run. No distinct pipelines required.
• Pest Framework Support: We are committed to supporting the frameworks your teams use. We’ve released and open-sourced a native reporter for Pest, bringing first-class PHP testing into the Qase ecosystem. View the repository.
• Unified Reporting Standard: We’ve implemented a consolidated Qase Report schema to standardize how data flows from your CI/CD pipelines into our platform, ensuring reliability regardless of the environment scale. View the repository.

February was about ensuring that Qase grows with you. Whether you are managing a monorepo with hundreds of microservices or a shared step library with thousands of assets, our goal is to provide the governance and structure you need to keep moving fast.

Happy testing!