Qase Blog

Introduction Testing is one of the few engineering activities that directly determines whether a company survives or collapses. When testing fails, it’s not just bugs that slip through. This failure might incur financial, operational, and reputational damage that will devastate the entire organization. Consider just a few examples: * In

The Problem: “Add support for iPhone 17 Pro and Android 16 Ultra” It’s the kind of update that looks harmless in the ticketing system: “Add support for iPhone 17 Pro and Android 16 Ultra across the test suite.” But you know better. That one sentence can mean hours of

Our beautiful Berlin QA community gathered again in early October, and even with autumn in full swing, around 70 people showed up for another great evening of ideas, demos, and honest conversations about quality. I’m so damn happy to see how this community has grown: familiar faces who’ve

Q3 was special. We took the feedback, ideas, and friction points from our community and channeled them into a focused push on three core fronts: simplifying your workflow, making our AI an indispensable partner, and giving you enterprise-grade control. The result? Some of our most impactful updates to date. Here's

Test automation is often treated as a checklist item: if you have it, great; if not, build it. But too many teams automate without knowing what value they expect, or how to measure whether the investment is paying off. That’s a problem. Because automation is an investment. Like any

Vitaly Sharovatov and Anupam Krishnamurthy investigate the Myth of Laziness in a new research paper, available for download now from Zenodo. Laziness as a Construct, Not a Trait Research across psychology, neuroscience, and organizational behavior shows that “laziness” is rarely an inherent trait. Instead, behaviors that look like disengagement usually

It’s 6:47 PM. The go-live is tomorrow. Your PM, Julia, leans over your desk:  “We’re sure the MFA flow was fully tested after that UI change, right?” A simple question but your mind races. That was ticket JIRA-4815. The original requirements are in a Confluence doc titled

Consistency in testing shouldn't be a constant struggle. It should be the default. We believe the key isn't to work harder, but to remove the friction that makes the work difficult in the first place. This month, we took a hard look at those time-consuming, repetitive tasks that get in

In the first article of this series, I focused on where AI is already proving useful in test automation: generating test cases and assisting with automation. In the second, I explored what’s still emerging: promising ideas like defect prediction and visual testing that work in some places but aren’