Testing
The RAG evaluation tooling landscape has exploded. RAGAS, TruLens, DeepEval, UpTrain, Arize Phoenix — there are at least a dozen frameworks claiming to be the definitive way to measure RAG quality. Evaluating the evaluators is its own non-trivial problem. Most teams pick the first framework they encounter, discover it does
Testing
Integration tests are slow, brittle, and expensive to maintain. You spin up multiple services, wire them together in a test environment, and hope that everything behaves the way it did last Tuesday. When a test fails, you spend twenty minutes figuring out whether the problem is in the consumer, the
Testing
Chunking is one of the most consequential decisions in any RAG system, and one of the least tested. Most teams pick a strategy, set a chunk size, and ship. Then they wonder why retrieval quality degrades on longer documents, or why the system can never answer questions that span multiple
Contract Testing
Consumer-driven contract testing is a testing approach where each consumer of an API defines what it expects from the provider, those expectations are captured as a contract, and the provider verifies it honors every consumer's contract before deploying. It prevents the most common microservices failure mode: API
Testing
Concordion and FitNesse both implement acceptance testing through executable specifications, but they make fundamentally different choices about how specs are written, where they live, and who maintains them. Choosing the wrong one creates friction that compounds over time. Core Philosophy FitNesse is a wiki. You run a standalone server, write
Testing
A Concordion specification is a readable document first and a test harness second. The commands embedded in the HTML are light enough that a product manager can understand the spec without knowing what they do. This post covers the full set of commands you will use day-to-day and
Testing
RabbitMQ's flexibility is also its testing challenge. You have exchanges, queues, bindings, routing keys, headers, and TTLs — all of which can be misconfigured in ways that swallow messages silently. A unit test that mocks the AmqpTemplate tells you nothing about whether your topology is correct. This post covers
Testing
The fixture class is where your Concordion spec connects to real application code. Getting the fixture structure right keeps your tests readable and maintainable as the spec grows. This post covers the patterns that work at scale. Basic Fixture Setup Every Concordion fixture class needs one annotation: import org.concordion.
Testing
RabbitMQ integration tests need a real broker to catch routing failures, binding misconfiguration, and dead-letter queue behavior that mocks will never surface. This guide covers testing exchanges, queues, bindings, and DLQs with Testcontainers — for both local development and CI pipelines. Key Takeaways Test the routing topology, not just message
Testing
Concordion ships with a small set of extensions that add screenshots, structured logging, and alternative spec formats to your output reports. You can also write your own. This post covers the four you will reach for most often. The @Extensions Annotation Extensions are declared on the fixture class using @Extensions.
Property-Based Testing
QuickCheck originated in Haskell in 1999 and remains the foundational property-based testing library. Its ideas have since spread to dozens of languages, but the Haskell version—and Erlang's commercial Quviq QuickCheck—represent the most mature implementations. This post covers advanced QuickCheck patterns that go beyond the introductory
Testing
qTest and TestRail are the two most commonly evaluated commercial test management tools. Both handle test case authoring, cycle management, and defect tracking, but they're built for different contexts. This comparison covers the practical differences — not the marketing copy — so you can make an informed decision. Who Makes