Do you plan to provide an extended Driver like UiAutomator2Options?
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 752
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 8
Description
Is there a reason why you do not provide extended drivers such as UiAutomator2Driver?
executeScript is flexible, but it is inconvenient to use multiple times.
For example, as follows
Current code
val result = driver.executeScript("mobile: {method-name}" mapOf(
"key1": "value1"
"key1": "value2"
))
Extended code
class UiAutomator2Driver(..): AndroidDriver(..) {
fun methodName(value1: String, value2: String) = executeScript(..)
}
UiAutomator2Driver().methodName("value1", "value2")
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue compares the current executeScript usage with a proposed UiAutomator2Driver and methodName API. Start by reviewing the existing driver API and how mobile scripts are exposed; done would mean deciding whether extended drivers should be provided and defining the supported interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, java, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100