📝 docs: add BDD implementation plan for pending tests
This commit is contained in:
44
bdd_implementation_plan.md
Normal file
44
bdd_implementation_plan.md
Normal file
@@ -0,0 +1,44 @@
|
|||||||
|
Pending BDD Tests Implementation Plan
|
||||||
|
|
||||||
|
Current Status:
|
||||||
|
- 54 scenarios total
|
||||||
|
- 30 scenarios passing
|
||||||
|
- 24 scenarios pending
|
||||||
|
- 0 scenarios undefined
|
||||||
|
|
||||||
|
Implementation Plan:
|
||||||
|
|
||||||
|
1. **JWT Secret Rotation Tests** (High Priority)
|
||||||
|
- Token validation with multiple valid secrets
|
||||||
|
- Secret rotation scenarios
|
||||||
|
- Graceful rotation during retention period
|
||||||
|
|
||||||
|
2. **JWT Secret Retention Tests** (High Priority)
|
||||||
|
- Automatic cleanup of expired secrets
|
||||||
|
- Secret retention based on TTL factor
|
||||||
|
- Maximum retention period enforcement
|
||||||
|
- Cleanup frequency configuration
|
||||||
|
|
||||||
|
3. **User Authentication Tests** (Medium Priority)
|
||||||
|
- Successful user authentication
|
||||||
|
- Failed authentication scenarios
|
||||||
|
- Admin authentication
|
||||||
|
- User registration
|
||||||
|
- Password reset functionality
|
||||||
|
|
||||||
|
4. **Configuration & Monitoring Tests** (Medium Priority)
|
||||||
|
- Configuration validation
|
||||||
|
- Metrics for secret retention
|
||||||
|
- Log masking for security
|
||||||
|
- Monitoring and alerting
|
||||||
|
|
||||||
|
Next Steps:
|
||||||
|
|
||||||
|
1. Implement JWT secret rotation logic in the authentication service
|
||||||
|
2. Add JWT secret retention and cleanup functionality
|
||||||
|
3. Implement user authentication and registration endpoints
|
||||||
|
4. Add configuration validation and monitoring
|
||||||
|
5. Implement step definitions for pending scenarios
|
||||||
|
6. Run full test suite to verify all scenarios pass
|
||||||
|
|
||||||
|
Estimated Time: 2-3 days
|
||||||
Reference in New Issue
Block a user