Review checklist for test automation code quality and best practices
Create a comprehensive code review checklist for test automation:
**Test Framework:** {{FRAMEWORK}}
**Language:** {{LANGUAGE}}
**Project Type:** {{PROJECT_TYPE}}
**Review Categories:**
1. **Test Structure:**
- [ ] Tests follow AAA pattern (Arrange-Act-Assert)
- [ ] Test names are descriptive and follow naming convention
- [ ] Each test validates one concept
- [ ] Tests are independent and can run in any order
2. **Code Quality:**
- [ ] No hardcoded values (use config/fixtures)
- [ ] DRY principle applied
- [ ] Proper abstraction levels
- [ ] No commented-out code
3. **Assertions:**
- [ ] Assertions are specific and meaningful
- [ ] Custom error messages where needed
- [ ] No empty catch blocks
- [ ] Proper assertion library usage
4. **Maintainability:**
- [ ] Page Object Model (if UI testing)
- [ ] Reusable helper functions
- [ ] Centralized selectors/locators
- [ ] Configuration externalized
5. **Reliability:**
- [ ] No hard sleeps/waits
- [ ] Proper synchronization
- [ ] Retry logic for flaky operations
- [ ] Clean setup/teardown
6. **Performance:**
- [ ] Tests run in reasonable time
- [ ] Parallel execution compatible
- [ ] No unnecessary operations
7. **Documentation:**
- [ ] Complex logic commented
- [ ] README updated if needed
- [ ] Ticket/requirement linkedOr press ⌘C to copy
Replace these placeholders with your own content before using the prompt.
[{FRAMEWORK][{LANGUAGE][{PROJECT_TYPE]