Merge branch 'dev/woopmnt-5249-e2e-ensure-version-coverage-for-woocommerce-and-php' into dev/woopmnt-5251-e2e-investigate-and-re-enable-woocommerce-blocks-e2e-tests

Author: mgascam

tests/e2e/README.md

@@ -11,12 +11,6 @@ The E2E tests use Playwright's built-in retry mechanism:
 - **Automatic retries**: Failed tests are automatically retried up to 2 times in CI
 - **Configurable**: Retries are enabled in CI (`retries: 2`) and disabled locally (`retries: 0`)
 
-
-### Improved Timeout Handling
-- **Increased timeouts**: UI interaction timeouts increased from 100ms to 10 seconds for better reliability
-- **Better error handling**: More robust page loading and element waiting strategies
-- **DevTools reliability**: Improved devtools page navigation and interaction
-
 ### Dynamic Matrix Generation
 - **L-1 Policy**: Tests automatically run against the latest WooCommerce version and the L-1 (previous major) version
 - **Dynamic version resolution**: Automatically fetches latest WC, RC, and beta versions from WordPress.org API
@@ -234,10 +228,6 @@ When tests fail in CI, Playwright's built-in retry mechanism automatically handl
 2. **Retry logs**: Look for retry attempts in the test output
 3. **Final results**: The test run will show the final result after all retry attempts
 
-This approach helps distinguish between:
-- **Flaky tests**: Tests that fail occasionally but pass on retry
-- **Consistent failures**: Tests that fail all retry attempts (indicating real issues)
-
 ## Slack integration
 
 The Slack reporter is a custom reporter that sends e2e test failures to a public Slack channel (search Slack channel ID `CQ0Q6N62D`). The reporter is configured to only send the first failure of a test to Slack. If the retry also fails it will not be sent to prevent spamming the channel.
@@ -285,16 +275,6 @@ await page.getByRole( 'button', { name: /submit/i } ).click();
 
 In some cases, you may need to wait for the page to reach a certain load state before interacting with it. You can use `await page.waitForLoadState( 'domcontentloaded' );` to wait for the page to finish loading.
 
-**What timeout values are used for UI interactions?**
-
-The E2E tests use optimized timeout values for better reliability:
-- **Global expect timeout**: 20 seconds (configured in `playwright.config.ts`)
-- **UI interaction timeouts**: 10 seconds for critical UI elements (buttons, forms, etc.)
-- **Page load timeouts**: 120 seconds for test execution
-- **Network idle waits**: Used for dynamic content loading
-
-These timeouts have been increased from the previous 100ms values to provide better stability, especially for slower environments or complex UI interactions.
-
 **What is the best way to target elements in the page?**
 
 Prefer the use of [user-facing attribute or test-id locators](https://playwright.dev/docs/locators#locating-elements) to target elements in the page. This will make the tests more resilient to changes to implementation details, such as class names.