Assertion Roulette

Multiple assertions without messages; unclear which failed.

Meszaros, xUnit Test Patterns

Signs of Use (Symptoms)

• Many expect() calls without descriptive messages.
• Test failure shows line number but not context.

Refactoring Solution

• One assertion per test (preferred).
• Add messages: expect(a).toBe(b, 'should have correct name').

Code example

Bad

Good