testing

TDD with Pest and Vitest follows the Red-Green-Refactor loop: write a failing test first, implement minimal code to pass it, then refactor. Pest handles PHP unit and feature tests; Vitest runs JavaScript tests. Both frameworks integrate with your test commands (composer test, npm run test) to validate your implementation continuously.

Yes. Playwright enables E2E test scenarios within a TDD workflow by automating browser interactions. You write failing E2E tests first, implement features to satisfy them, then refactor. This applies the same Red-Green-Refactor cycle across your full stack alongside unit and component tests.

Unit tests validate individual functions or methods in isolation using Pest or Vitest. Component tests verify UI components render and behave correctly. E2E tests use Playwright to test complete workflows from the user's perspective. TDD applies to all three, catching defects at different layers of your application.

Run your full test suite with coverage reporting (composer test or npm run test with coverage flags). TDD improves coverage by design—writing tests before code ensures every feature has validation. Monitor coverage metrics and identify untested paths, then write tests to close gaps and maintain confidence.

Yes. Use Pest for PHP testing (unit, feature tests) and Vitest for JavaScript testing, each with their native test runners. Execute both suites separately (composer test, npm run test) or combine them in CI/CD. This keeps your TDD feedback loop consistent across your full stack.

For PHP: composer test or php artisan test with Pest. For JavaScript: npm run test with Vitest. For E2E: Playwright runs via npm scripts. Execute these commands repeatedly in your TDD loop—after writing a failing test, after implementing code, and after refactoring—to validate each cycle.