Skip to content

feat: add the autoLaunch option to UiAutomator2Options and XCUITestOptions - #2473

Closed
theluckystrike wants to merge 1 commit into
appium:masterfrom
theluckystrike:feat/2222-auto-launch-option
Closed

theluckystrike wants to merge 1 commit into
appium:masterfrom
theluckystrike:feat/2222-auto-launch-option

Conversation

@theluckystrike

Copy link
Copy Markdown
Contributor

Fixes #2222

java-client 8.x had AndroidMobileCapabilityType.AUTO_LAUNCH, but the 9.x options classes don't have a typed method for autoLaunch, so callers fall back to amend("autoLaunch", ...). The capability's still documented for both the UiAutomator2 and the XCUITest drivers.

This adds SupportsAutoLaunchOption next to the other shared options in remote.options, with autoLaunch(), setAutoLaunch(boolean) and doesAutoLaunch(). UiAutomator2Options and XCUITestOptions both implement it.

OptionsBuildingTest gets one case per class that checks the unset, enabled and disabled states. Checkstyle passes and the options tests pass on JDK 25.

@mykola-mokhnach

Copy link
Copy Markdown
Contributor

This capability is not there deliberately. It should be deprecated and removed from corresponding drivers

@theluckystrike

Copy link
Copy Markdown
Contributor Author

Understood, thanks for explaining. I didn't know autoLaunch was on its way out, so I'll leave it alone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Revert AUTO_LAUNCH capability to options

2 participants