Avoid conditionals and loops in test logic

Avoid conditionals and loops in test logic | BeforeMerge Rules | BeforeMerge

Why this matters

if/for/computed expected values in a test can replicate the same mistake as the code under test, letting both agree on a wrong answer. Prefer literal, hard-coded expectations and parameterized cases over branching.

// Bad — computes the expectation the same way as the code
expect(sum(list)).toBe(list.reduce((a, b) => a + b, 0));
 
// Good — literal expectation
expect(sum([1, 2, 3])).toBe(6);

Why This Matters

Related Rules

Catch this automatically on every PR

Why this matters