Amend docs

Author: mgascam

tests/e2e/README.md

@@ -7,9 +7,9 @@ E2E tests can be run locally or in GitHub Actions. Github Actions are already co
 ## Recent Improvements
 
 ### Retry Mechanism
-The E2E tests now include an intelligent retry mechanism that:
-- **First run**: Executes all tests normally
-- **Automatic retry**: If any tests fail, only the failed tests are retried using Playwright's `--last-failed` flag
+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
@@ -229,14 +229,9 @@ You can use the locator functionality to help correctly determine the locator sy
 
 When tests fail in CI, the retry mechanism automatically kicks in:
 
-1. **First run**: All tests execute normally
-2. **If failures occur**: The system automatically retries only the failed tests
-3. **Retry logs**: Look for the message "Some tests failed, retrying only failed tests with --last-failed flag" in the logs
-4. **Final results**: The test run will show both the initial results and retry results
-
-This approach helps distinguish between:
-- **Flaky tests**: Tests that fail occasionally but pass on retry
-- **Consistent failures**: Tests that fail both initially and on retry (indicating real issues)
+1. **Automatic retries**: Failed tests are automatically retried up to 2 times
+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
 
 ## Slack integration