1. Automated software tests are codified requirement constraints and usage definitions
2. If you don't have constraints and usage defined, you can't write meaningful or valuable tests
3. An implemented module is not equivalent to constraint and usage definitions
2. If you don't have constraints and usage defined, you can't write meaningful or valuable tests
3. An implemented module is not equivalent to constraint and usage definitions
Comments
- constraints and usage are not defined, or the those are so volatile that many tests are invalidated and thrown out
- they already wrote a unit first, then must retroactively define its constraints and usage