Testing
When tests contain domain concepts that don't map cleanly to built-in RSpec matchers, the result is verbose assertions that reveal implementation rather than intent. Custom matchers let you express what the test means rather than how it works. A matcher like be_a_valid_invoice communicates more
Ruby Testing
Good RSpec tests are fast, readable, and fail for the right reasons. Bad ones are slow, coupled to implementation, full of mocks, and when they fail you can't tell what's broken. This post covers the conventions and patterns that separate maintainable RSpec suites from the ones
Test Management
A defect lifecycle is the sequence of states a bug passes through from discovery to confirmed resolution. Teams that manage this well ship faster: bugs get fixed in priority order, regressions get caught before release, and nothing falls through the cracks. Teams that don't manage it well accumulate
Test Automation
A growing share of traffic hitting business websites isn't a person clicking around — it's an AI agent filling out a form, submitting a product to a directory, or calling an API on a user's behalf. These agents follow the same UI and API contracts
Test Automation
Software testing isn't a "tech company problem." Any business with a website that takes orders, shows a price, or captures a lead has software that can break — and the cost of that breakage doesn't care whether you sell SaaS subscriptions or custom window blinds.
Embedded Testing
Robot software is some of the hardest software to test. It's concurrent, time-sensitive, hardware-dependent, and the behavior emerges from complex interactions between perception, planning, and control. Yet untested robot software fails in the real world — sometimes expensively. ROS2 (Robot Operating System 2) provides a testing framework
Testing
Shipping LLM features without automated evaluation is like deploying code without running tests. DeepEval and Promptfoo are the two leading open-source frameworks for automating LLM evaluation — they let you define quality metrics, run them against your prompts, and fail CI when quality drops. This guide covers both tools: what
Testing Tools
The hardest part of shipping software is not writing it — it's knowing whether what you shipped is working. Deployment pipelines that run tests, pass CI, and complete without errors frequently deploy broken software. The tests passed because they tested the wrong things, or because the production environment differs
Testing
Every QA course teaches equivalence partitioning, boundary value analysis, and decision tables as if they're interchangeable. They're not. Each technique targets a different class of defect. Using the wrong one wastes time. Using only one leaves gaps. This post explains what each technique actually catches, when
Test Automation
You know test automation is worth investing in. The question is how to prove it to someone who controls the budget. Engineering managers and executives don't respond to "it's best practice" or "everyone does it." They respond to numbers. Specifically: what does
Testing
Most examples of decision tables use two or three conditions. Real business rules rarely do. Insurance eligibility, loan approval, tax calculation, shipping logic — these systems have five, six, seven conditions, each interacting with the others. The naive approach — enumerate every combination — produces tables with 128 or 256 columns that nobody
Testing
Decision tables are one of the oldest, most reliable test design techniques in existence — and one of the most underused. QA engineers reach for exploratory testing or equivalence partitioning and forget that for systems with complex conditional logic, a decision table gives you something those techniques can't: a