drupal-major-upgrade-validation

Automate Drupal major upgrade validation by capturing a behavioral baseline on the current stable version, applying the upgrade, and re-running the same Playwright browser checks on the upgraded site. It generates a structured comparison report detailing frontend and backend differences.

Yes, you can validate a Drupal D10 to D11 upgrade path with Playwright. The workflow requires a two-branch setup, using drush for container orchestration and AGENTS.md guidance, to execute page checks and verify functionality across major version jumps.

The best way to compare frontend behavior across a Drupal major version upgrade is browser-driven validation. Capture a baseline on the stable branch, apply the upgrade, and run the identical test plan to produce a detailed comparison report.

Yes, Drupal major upgrade validation requires a two-branch workflow. You run baseline tests on the current stable branch, then apply the upgrade and execute the same test plan on the upgraded branch to identify behavioral regressions.

Yes, you need drush and container orchestration to test a Drupal major version upgrade. The validation process relies on drush for applying the upgrade and AGENTS.md guidance for orchestrating the container environment during Playwright page checks.

A limitation of this Drupal major upgrade validation is its dependency on a strict two-branch workflow and Playwright-based browser automation. It targets browser-driven validation scenarios, so backend-only CLI tests without a frontend component may not be fully covered.