dev-workflow

To enforce a TDD development workflow for non-trivial code changes, you follow a structured process of requirement understanding, ripple-effect analysis, test writing, implementation, local verification, and self-review to ensure disciplined practices.

The best way to integrate Playwright UI testing into a CI/CD pipeline is to run it as a verification step after implementation and local checks, ensuring frontend functionality is validated before committing and deploying to production environments.

Yes, disciplined test-driven development requires post-deployment production verification. After local verification and commits, you must perform checks in staging and production environments to confirm production readiness and catch deployment issues.

To conduct an AI-assisted code review before committing new features, you initiate a self-review phase after local verification, checking code quality and adherence to standards before proceeding to the final commit and deployment stages.

You should perform ripple-effect analysis during test-driven development immediately after understanding requirements and before writing tests, allowing you to map the full impact of code modifications across the system prior to implementation.