woo-beta-compat-test

# WooCommerce Beta Compatibility Test ## Overview Run a full compatibility test of the released plugin against a new WooCommerce beta version. This covers QIT automated tests, GitHub Actions CI, and manual Playwright smoke tests. ## Usage Invoke with the WooCommerce beta version as argument: ``` /woo-beta-compat-test 10.6.0-beta.1 ``` ## Process Follow all four steps sequentially. Report results after each step before moving to the next. ### Step 1 — Download the latest stable plugin zip Download the currently released version from wordpress.org: ```bash curl -L -o /tmp/woocommerce-google-analytics-integration.zip \ "https://downloads.wordpress.org/plugin/woocommerce-google-analytics-integration.latest-stable.zip" ``` Verify the download succeeded and the file is a valid zip. ### Step 2 — Run QIT commands Run these three QIT commands with the downloaded zip. Use the exact beta version provided by the user first. Only if a version is not available, fall back to the `X.Y.Z-dev` format (e.g., `10.6.0-beta.1` → `10.6.0-dev`). Use `--help` on the failing command to discover available versions. **Note:** Each command uses different flags — pay attention to the differences. ```bash # run:activation uses --source (not --zip) and --woo for version qit run:activation \ --woo "<VERSION>" \ --source /tmp/woocommerce-google-analytics-integration.zip \ woocommerce-google-analytics-integration # run:woo-api uses --zip and --woocommerce_version, supports --wait qit run:woo-api \ --woocommerce_version="<VERSION>" \ --zip /tmp/woocommerce-google-analytics-integration.zip \ --wait \ woocommerce-google-analytics-integration # run:woo-e2e uses --zip and --woocommerce_version, supports --wait qit run:woo-e2e \ --woocommerce_version "<VERSION>" \ --zip /tmp/woocommerce-google-analytics-integration.zip \ --wait \ woocommerce-google-analytics-integration ``` The `--woocommerce_version` flag on `run:woo-api` and `run:woo-e2e` only accepts specific enumerated values (check `--help` output). If the beta version is not listed, use the `-dev` suffix version instead. After each command completes, analyze the report output. Summarize pass/fail status and highlight any failures with details. ### Step 3 — Trigger GitHub Actions and wait for results Trigger both CI workflows with the beta version and wait for completion: ```bash gh workflow run e2e-tests.yml \ -f wc-rc-version="<VERSION>" gh workflow run php-unit-tests.yml \ -f wc-rc-version="<VERSION>" ``` After triggering: 1. Use `gh run list --workflow=<workflow>` to find the run IDs 2. Use `gh run watch <run-id>` to wait for each run to complete 3. If a run fails, fetch the logs with `gh run view <run-id> --log-failed` 4. Analyze the failure logs and report what went wrong 5. If the failure is in plugin code, suggest or apply a fix ### Step 4 — Playwright smoke tests Start the local WordPress environment with the WooCommerce beta installed: ```bash npm run wp-env:up npm run build npm run -- wp-env run cli --config=.wp-env.test.json -- wp plugin update woocommerce --version="<VERSION>" npm run -- wp-env run cli --config=.wp-env.test.json -- wp wc update ``` Then use the Playwright MCP browser to perform these smoke tests: 1. **Settings page** — Navigate to `wp-admin` (user: `admin`, pass: `password`), go to WooCommerce → Settings → Integration → Google Analytics. Verify the settings page loads without errors. 2. **Save settings** — Enter a test tracking ID (`G-TEST12345`), save. Verify settings persist after reload. 3. **Frontend GA snippet** — Navigate to the shop page. View page source or inspect the HTML to verify the gtag.js snippet is present with the correct tracking ID. 4. **Product page** — Open any product page. Verify it loads without errors and the GA snippet is present. 5. **Add to cart** — Add a product to the cart. Verify the cart updates and no JS errors appear in the console. Report the result of each check. If any check fails, provide details and screenshots. ## After testing Summarize all results in a table: | Test | Status | Notes | |------|--------|-------| | QIT Activation | ✅/❌ | | | QIT API | ✅/❌ | | | QIT E2E | ✅/❌ | | | GH Action: E2E Tests | ✅/❌ | | | GH Action: PHP Unit Tests | ✅/❌ | | | Smoke: Settings page | ✅/❌ | | | Smoke: Save settings | ✅/❌ | | | Smoke: Frontend GA snippet | ✅/❌ | | | Smoke: Product page | ✅/❌ | | | Smoke: Add to cart | ✅/❌ | | ## Error triage When any test fails, classify each error into one of three categories and take the corresponding action: ### 1. Plugin error — fix it The error is in code from this repository (e.g., a PHP fatal in `includes/`, a JS error from `assets/`, a failing unit test in `tests/`). **Action:** Fix the issue directly in the codebase. Run the failing test again to confirm the fix. ### 2. QIT / test environment error — report to #qit The error is related to the QIT tool itself or the testing environment (e.g., QIT command crashes, Docker/environment setup failures, test infrastructure timeouts, flaky QIT test runner behavior unrelated to plugin code). **Action:** Draft a Slack message for the `#qit` channel describing the error, the QIT command that was run, and the full error output. Ask the user to send the message to the coresponding channel. ### 3. WooCommerce / other plugin error — report to #woo-core-releases The error is caused by WooCommerce core or another plugin (e.g., a WooCommerce API regression, a breaking change in WC beta, a failure in a WC core E2E test unrelated to this plugin's code). **Action:** 1. Use the context-a8c MCP to identify which team owns the affected area (search Linear, Slack, or Matticspace for the relevant WooCommerce component) 2. Draft a Slack message for the `#woo-core-releases` channel describing: - The WooCommerce beta version being tested - The specific error and which test surfaced it - A ping to the responsible team identified above 3. Ask the user to review and send the message