tdd

Use when implementing or changing behavior that callers or users can observe: a new feature, a behavior change, a bug fix whose cause is known, a port from a reference implementation, or a new or changed public interface or seam. Drives the work through a red-green-refactor loop over a frontier of behaviors, with tests at the public interface. Do not use for changes with no behavior to prove, such as configuration, documentation, formatting, or mechanical renames; for disposable prototypes or spikes; for a bug whose cause is still unknown, which needs diagnosis first; for reviewing existing changes; or for conceptual questions about TDD.

License

MIT