Lint
Lint checks code without running it. It finds likely bugs, unsafe patterns, style issues, and broken project rules.
Another example
Before review, lint finds an unhandled Promise, an inaccessible image, and an import from a server-only module.
Main parts
- 01Code or behavior under test
- 02Observable evidence
- 03Coverage, failure, and recovery
Use it when
Run stable rules in editors and CI. Limit automatic fixes to safe, predictable changes.
Do not use it when
Do not enable noisy rules, treat lint as tests, or fix unrelated files during focused work.
Name used in code
AST rules + diagnostics + optional autofix Before you ship
Check the environment and prepared test data (fixture). Define a result you can observe, failure and edge cases, isolation, stable inputs, useful error details, and cleanup. Set a time budget, owner, and flaky-test rule.
Outcome: Use Lint to gather repeatable evidence about this behavior or quality risk. User context: Before review, lint finds an unhandled Promise, an inaccessible image, and an import from a server-only module. Validation approach: Lint. Why it fits: Run stable rules in editors and CI. Limit automatic fixes to safe, predictable changes. Do not use it when: Do not enable noisy rules, treat lint as tests, or fix unrelated files during focused work. Test requirements: Name the system and test environment. Define prepared test data, other inputs, and the result you can observe. Include failure and edge cases, allowed error, isolation, and cleanup. Test operations: Make failures easy to diagnose. Control random or changing inputs. Name an owner. Keep the test fast and simple enough for its release gate. Acceptance criteria: The test fails for the known bug and passes after the fix. It repeats in the target environment, gives useful evidence, and does not expose or change unrelated data. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Release gate, environment, prepared test data, allowed error, time budget, owner, and flaky-test rule.
Check this request
Review the current use of Lint. Definition: Lint checks code without running it. It finds likely bugs, unsafe patterns, style issues, and broken project rules. Release checks: Check the environment and prepared test data (fixture). Define a result you can observe, failure and edge cases, isolation, stable inputs, useful error details, and cleanup. Set a time budget, owner, and flaky-test rule. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.