Testing accompanies the whole cycle
Good testing does not wait until the end: it starts with reviewing requirements and continues in each phase. The earlier QA gets involved, the cheaper it is to fix (shift-left). That is why every work product (requirements, design, code) can and should be reviewed.
- Requirements: static review to detect ambiguities.
- Design: review of architecture and edge cases.
- Code: reviews and component tests.
- Integrated system: integration and system tests.
- Before deployment: acceptance tests.
A well-defined acceptance test in the requirements phase serves both as an acceptance criterion and as a test case.
QuestionToca para voltear
When should testing start in a project?
Reviewing requirements to detect ambiguities is an example of…