How to write tests retrospectively for existing code?
Open
question
- Dominant language
- Rust
- Stars
- 826
- Forks
- 133
- PR merge metrics
- No merged PRs in 30d
Description
When a project has been written/deployed _without_ tests, what is the recommended approach for writing _retrospective_ tests?
Contributor guide
Research direction
Start by reviewing the book's existing testing, TDD, and BDD sections to see whether retrospective testing is already covered. Define the recommended approach for projects deployed without tests, and consider the documentation complete when it gives readers a practical, ordered path for adding tests to existing code.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, testing
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100