Test names are descriptive

When a test fails in CI, the first signal is the test name. A name like test 1 or should work tells the developer nothing: which behavior failed, which input triggered it, which component is broken. AI-generated test scaffolding frequently produces placeholder names that were never replaced. The result is a test suite where CI failure messages require reading test bodies to understand what broke — slowing down incident response and increasing the chance a developer ignores the failure. ISO-25010:2011 maintainability requires that tests communicate intent clearly.

Replace any test name under 5 characters or matching patterns like test 1, foo, should work, or empty strings with a name that describes the specific behavior and expected outcome. The name should complete the sentence "It...":

// Before: meaningless in CI output
it('test 1', () => { ... })
it('test 2', () => { ... })

// After: CI failure message is self-explanatory
it('rejects signup with duplicate email', () => { ... })
it('returns 404 when user does not exist', () => { ... })