Handle headless CI runners in browser find focus UI test
On WarpBuild runners without a GUI session, XCUIApplication.launch() blocks ~60s then fails with "Failed to activate application (current state: Running Background)". Wrap launch() in XCTExpectFailure so the test can continue — keyboard and element APIs work via accessibility even when the app is in .runningBackground. Increase test execution time allowance from 120s to 180s to account for the 60s activation timeout on headless runners. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
381aab0d83
commit
b5fb304af0
2 changed files with 19 additions and 14 deletions
2
.github/workflows/ci.yml
vendored
2
.github/workflows/ci.yml
vendored
|
|
@ -689,7 +689,7 @@ jobs:
|
|||
-clonedSourcePackagesDirPath "$SOURCE_PACKAGES_DIR" \
|
||||
-disableAutomaticPackageResolution \
|
||||
-destination "platform=macOS" \
|
||||
-maximum-test-execution-time-allowance 120 \
|
||||
-maximum-test-execution-time-allowance 180 \
|
||||
-only-testing:cmuxUITests/BrowserPaneNavigationKeybindUITests/testCmdFFocusesBrowserFindFieldAfterCmdDCmdLNavigation \
|
||||
test-without-building
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue