Qase Blog

Many years ago, while working for a bank, I was a member of the techleads guild. Being a guild member in large companies often comes with the responsibility to interview people, and I interviewed a lot. Sometimes I had up to twelve interviews a week. I still shudder remembering these

Amsterdam gave us the usual November package: cold, grey, a bit of rain. But inside the JetBrains office it was warm, bright, and full of people who actually like talking about testing, which is all I really need. More than 40 folks showed up, grabbed some pizza, found their spots,

Introduction As we've already covered in the article about Network Profiler, Qase provides powerful tools for monitoring and analyzing test scenarios. In this article, we'll explore another important profiler: Sleep Profiler, which helps identify and optimize the use of delays in tests. The Problem with Using Sleep in E2E Tests

Introduction In modern software development, tests often interact with external APIs and services via HTTP requests. To effectively debug and analyze test scenarios, it’s crucial to have full visibility into all network interactions. Qase provides a powerful tool, the Network Profiler, which automatically intercepts and logs all HTTP requests

October was about turning the dial up on confidence. In quality assurance, the greatest drain isn't the work itself. It's the nagging doubt: Did I update all the test cases? Will the AI fail this run? Is this data secure for my next audit? We heard you. This month, we

AI in software testing: real capabilities, real limits Artificial intelligence is already embedded in modern software testing, from generating test cases and stabilizing UI automation to prioritizing tests in CI/CD pipelines. At the same time, bold claims about autonomous AI testers and self-directed test agents continue to outpace reality.

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