An evaluation suite is a set of tests that checks software behavior and quality. It prevents rework when tests target meaningful risks; tests coupled to implementation, slow to run, or unreliable can instead create maintenance work and delay delivery. section 5.0 section 5.1
Assess a suite by asking:
- Would failure catch a defect that could reach users? section 5.1
- Does the test fail when behavior breaks, rather than during a safe refactor? section 5.1
- Does it run quickly enough to use locally and on every commit? section 5.1
- Do developers trust failures, or do they rerun or ignore them? section 5.0 section 5.1
Listing 5.1 A contrast between a wasteful test and a value-adding test
# Waste: tests implementation details
def test_payment_uses_token_bucket_limiter():
processor = PaymentProcessor()
processor.process(payment_request)
assert isinstance(processor.limiter, TokenBucketRateLimiter)
assert processor.limiter.calls == [call(rate=100, burst=10)]
# Value: tests behavior
def test_payment_respects_rate_limits():
processor = PaymentProcessor()
results = [processor.process(payment_request) for _ in range(150)]
passed = sum(1 for r in results if r.success)
rate_limited = sum(1 for r in results if r.rate_limited)
assert passed <= 110 # allows burst
assert rate_limited >= 40Compare a payment test that asserts a specific rate-limiter implementation with one that checks whether payments respect rate limits. The behavior-focused test can remain useful when the implementation changes. section 5.1





















