validate-patch

To validate a Drupal patch before submitting, run coding standards, static analysis, and test coverage quality gates inside a DDEV-backed project worktree to ensure all checks pass. This process resolves the project root, executes phpcs, phpstan, and phpunit, and reports pass/fail results with actionable failure details.

Drupal code review quality gates include PHPCS for coding standards, PHPStan for static analysis, and PHPUnit for tests and coverage. Running these checks in a DDEV environment ensures consistent results by mirroring the project's actual configuration before opening a merge request.

Yes, patch validation works with DDEV containers by executing phpcs, phpstan, and phpunit directly inside the DDEV environment. It resolves the project root from a configuration file and uses a database snapshot before running tests for fast rollback and retries.

To prevent brittle tests during Drupal patch validation, perform a pre-test design review that flags risky test patterns and inheritance issues before containers spin up. This review identifies assertions that break under normal Drupal behavior prior to executing the test suite.

Yes, you can target specific files for static analysis and coding standards checks in a Drupal worktree using optional targeted file validation. This allows you to run phpcs and phpstan on individual changed files rather than the entire project codebase.

Drupal patch validation fails PHPUnit tests by design when code changes introduce regressions, reporting actionable failure details for each broken assertion. The validation process snapshots the database before tests to allow fast rollback and retries without manual environment resets.