Quality assurance guides — processes, tools, and techniques for building and running an effective QA practice.
Testing Tools
Most web analytics tools tell you what happened: 12% of users dropped off on the checkout page. FullStory tells you why: those users clicked the submit button, waited six seconds for a response that never came, clicked again, got a duplicate order error, and left. Every element interaction, every page
Testing Tools
Mobile apps crash in ways that web applications don't. The device environment is fragmented — hundreds of device models, multiple OS versions, varied memory configurations, inconsistent network conditions. A crash that affects Samsung Galaxy S21 devices running Android 12 with 6GB RAM during low-memory conditions might never occur
Exploratory Testing
Session-based test management (SBTM) was invented by Jonathan and James Bach in 2000 to solve a real problem: exploratory testing was producing great bug finds but terrible accountability. Managers couldn't answer basic questions — how much testing was done, what was covered, where did testers spend their time?
Exploratory Testing
Exploratory testing without risk framing is random. Risk-based exploration is deliberate: you identify the failure modes that matter most, then hunt them specifically. The distinction matters because testing time is always limited. Risk framing ensures you spend it on what's most likely to hurt you. What Risk
Exploratory Testing
Exploratory testing is often a solo activity. One tester, one charter, 90 minutes. It works. But pairing changes the dynamic in ways that matter: you find different bugs, you find them faster, and you build shared understanding of the system. Pairing isn't just "two people looking at
Exploratory Testing
A charter is the mission statement for an exploratory testing session. Done right, it focuses a tester's attention without scripting their behavior. Done wrong, it produces either aimless wandering or checkbox execution. Writing good charters is a skill. This post covers the mechanics. The Charter Formula The standard
Exploratory Testing
Most teams classify bugs by severity and priority. Useful, but limited. A severity scale tells you how bad a bug is. It doesn't tell you what kind of bug it is, why it happened, or where to look for similar ones. Bug taxonomies fill that gap. A well-
Test Design
Equivalence partitioning for a single input is straightforward: identify the behavioral regions, pick one representative from each. Multi-variable and stateful systems are harder because the partitions aren't independent — the valid values for one variable depend on the state of another. This post covers EP for systems with
Test Design
Most equivalence partitioning (EP) tutorials use age ranges and temperature thresholds. Clean, numeric, easy to understand. The real world is messier: username validation, date ranges with timezone edge cases, enum state machines, and variable-length collections. This post covers EP for non-numeric input types where the partition boundaries aren&
Testing Tools
Most developers know Sentry as an error tracker. When an exception is thrown, Sentry captures it, groups it with similar errors, and notifies the team. This basic use case is valuable, but it covers only a fraction of what Sentry can do. Sentry's platform has expanded significantly in
Sanity Testing
"Sanity testing and smoke testing are the same thing." — every QA team that's never had a proper conversation about testing terminology. They're not the same. They serve different purposes, trigger at different points, cover different scopes, and fail for different reasons. Conflating them leads
Sanity Testing
Sanity testing is the most misunderstood testing type in the QA vocabulary. Teams confuse it with smoke testing, use the terms interchangeably, or skip it entirely in favor of running the full regression suite. All of these are mistakes. This guide explains what sanity testing actually is, when it'