How to Write a Test Case (Quick Checklist)
A well-written test case follows a clear, repeatable structure. Use this checklist to create consistent and traceable test cases.
1. Test Case ID – Assign a unique identifier for traceability.
2. Title / Description – Clearly define the objective and functionality under test.
3. Preconditions
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
There's a specific kind of exhaustion that comes from knowing exactly what needs to be done, but the tools won't let you do it efficiently. You've got the vision—automated test coverage across three projects, a clean migration path, tests that actually reflect production—but between you and that vision
That's not a typo. That's the number of test results you sent to Qase in 2025.
If you shipped code this year, you know the grind. But as we look back at the Qase ecosystem, the sheer scale of what you all built (and protected) is staggering.
This wasn't just
Introduction
As covered in the articles on Network Profiler and Sleep Profiler, Qase provides powerful tools for monitoring and analyzing test scenarios. This article explains Database Profiler—a tool that automatically tracks and logs database operations.
The Problem with Databases in Tests
In integration and E2E tests, the database is
Inside Brandon DePesa’s journey from startup spreadsheets to unified, data-driven quality at SUSE
SUSE is one of the most recognizable names in computing, from open source to enterprise. In its cloud-native business, Rancher Prime is the centerpiece: a platform for Kubernetes cluster provisioning and management.
For many customers, their
Ages ago, I applied for a software developer job, and after a short briefing the recruiter sent me a link to an MBTI profiling service. I smiled and politely rejected the opportunity.
Most engineers I know laugh at pseudo-scientific "psychological" profiling like MBTI / DISC, and laugh even harder at folks
Our Berlin QA community got together again for what was actually our 10th meetup. Ten evenings of talking about quality, risk, weird edge cases, all about the beautiful work of setting order in messiness.
I keep saying this, but it is still true every time. I am really happy to
We’re approaching the end of the year, but we aren't slowing down. If anything, November was about acceleration. We looked at the workflows that engineers use every day and asked: "How can we make this feel instant?"
This month, we’re introducing a new architecture for shared logic, a
