Qase Product Updates: May 2026

Shipping software that holds up is genuinely hard, and the people who do it well rarely get enough credit. Whether quality is owned by a dedicated QA team or shared across your engineers, the job comes down to the same thing: catching what matters before your users do, without slowing the release down.

We get to build some of the tools you rely on to do that, and we take it seriously. Every month the aim is the same, make them a little better and a little less in your way. In May, most of that work came down to connection: reaching the apps running on your own machines, putting test results where your team already talks, and giving you finer control over who can do what. Underneath all of it, the platform carried more load than it ever has.

Here is what we shipped.

Pillar 1: Bridging Private Networks with Cloud Automation

Testing applications that run on your local machine or behind a corporate firewall can be a frustrating exercise. You want to run cloud-based browser tests or AI-driven test generation, but setting up a secure pathway into your private network usually involves complex workarounds.

The Qase Tunnel: Private, Local, and Secure

To resolve this, we launched the Qase Tunnel. This is a secure, supported utility that lets our cloud execution engine reach applications on your local machine or private network.

It replaces our older qase-frp script and addresses its main limitations:

• Multi-Host Routing: If your application redirects from a local address to another internal host, the connection stays intact and routing continues.
• Workspace-Level Privacy: The tunnel is fully private to your organization. It does not publish anything to the public web, and only members of your authenticated Qase workspace can access it.

To start a tunnel, you run a single command in your terminal:

qase-tunnel start

Once active, you select the tunnel in your environment settings and run your automated tests.

Pillar 2: Shared Visibility in Your Chat Channels

Quality is a shared responsibility, and visibility shouldn't be gated behind separate tools. When testing updates land where your team already communicates, feedback loops shrink and collaborative debugging happens naturally.

In May, we launched native integrations for two major platforms to bring testing

events straight into your chat channels.

Discord Integration

For startups, AI-focused teams, and developer communities who coordinate in Discord, you can now pipe Qase workspace events directly into your server. It takes a few clicks to set up in your App settings, allowing the entire team to see test run updates in real time.

Mattermost Integration

For teams with strict data residency requirements, such as fintech, healthcare, and defense organizations, we built a native Mattermost integration. Since Mattermost runs behind your own firewall, you can now route test runs, defects, and milestone updates directly into your self-hosted channels without compromising security.

Pillar 3: Safe Collaboration with Granular Permissions

When developers, product owners, and quality specialists all contribute to a

single repository, you need to be able to delegate control without creating

step-on-toes anxiety. Good governance tools help your team collaborate with

confidence.

Based on your feedback, we split and expanded our workspace permissions:

• Schedule vs. Execute: You can now grant the permission to schedule runs separately from execution rights.
• Create vs. Update: We split the old project "save" permission. Anyone on the team can draft new test cases without the risk of accidentally overwriting your established, baseline test.
• Dashboard Sharing: A dedicated permission now controls who can generate public sharing links for dashboards, protecting sensitive internal quality metrics.

Pillar 4: Platform Performance and Feedback Loops

5 Million Public API Calls

On May 4th, our public API crossed 5 million calls in a single day, which represents a 60% jump in just four weeks.

We share this because we are proud of the scale of automation our users are building on Qase. This volume means our systems are handling heavy, continuous CI/CD load from real development pipelines. This traffic helps us find and fix subtle performance bottlenecks, ensuring that Qase remains a reliable foundation for your team's deployments.

Direct AI Feedback Loop

We want to ensure our AI features are working reliably for your specific codebases. To help us improve, we have added a direct feedback form inside our AI testing interface. If a step doesn't generate correctly, you can report it with one click. The data goes directly to our internal engineering channel so we can iterate on the models based on your real-world usage.

Faster Dashboards and Sharper Monitoring

We migrated more of our analytical dashboards to a faster query engine, which means quicker load times when you are working with complex metrics. Behind the scenes, we also added deeper traffic monitoring and alerting so we can catch performance bottlenecks early, often before they ever reach you.

In May, we worked on the connection points that keep an engineering team running smoothly. Securing local tunnels, routing updates to Mattermost, and balancing permissions all serve the same goal: making quality a natural, low-friction part of your daily development process.

Happy testing!