appium-espresso-driver 2.15.1 → 2.15.2

package/CHANGELOG.md

@@ -1,3 +1,10 @@
+## [2.15.2](https://github.com/appium/appium-espresso-driver/compare/v2.15.1...v2.15.2) (2023-02-04)
+
+
+### Miscellaneous Chores
+
+* add print espresso path as a command ([#854](https://github.com/appium/appium-espresso-driver/issues/854)) ([5402b5f](https://github.com/appium/appium-espresso-driver/commit/5402b5f1ddc5e2f1555d4fe90031e3f6cbc2078d))
+
 ## [2.15.1](https://github.com/appium/appium-espresso-driver/compare/v2.15.0...v2.15.1) (2023-01-17)
 
 

package/README.md

@@ -40,6 +40,10 @@ On top of standard Appium requirements Espresso driver also expects the followin
 - The package under test must not have mangled class names (e.g. [Proguard](https://developer.android.com/studio/build/shrink-code) must not be enabled for it)
 
 
+## Scripts
+
+- `appium driver run print-espresso-path` prints the path to the Appium Espresso server root. You can modify the gradle file directly if [Espresso Build Config](#espresso-build-config) was not sufficient.
+
 ## Capabilities
 
 ### General
@@ -191,6 +195,9 @@ driver | 'compose' or 'espresso' | The name of the subdriver to use for elements
 
 [Jetpack Compose](https://developer.android.com/jetpack/compose) is Android’s modern toolkit for building native UI. Espresso driver supports basic interactions with Compose-based applications since version *1.46.0*.
 
+[Appium UiAutomator2 driver](https://github.com/appium/appium-uiautomator2-driver/) allows to interact with Jetpack Compose elements via the accessibility layer by providing [testTag](https://developer.android.com/reference/kotlin/androidx/compose/ui/platform/package-summary#(androidx.compose.ui.Modifier).testTag(kotlin.String)) modifier attribute or the displayed text, but this Espresso driver allows you to access Jetpack Compose elements directly.
+
+
 ### Interaction With Compose Elements
 
 Espresso driver has the concept of subdrivers. This works quite similarly to the concept of contexts, while contexts are used to switch between native and web, and subdrivers are still
@@ -203,7 +210,7 @@ In order to change between subdrivers use the [driver](#settings-api) setting. S
 - click, isDisplayed, isEnabled, clear, getText, sendKeys, getElementRect, getValue, isSelected: These commands should properly support compose elements.
 - getAttribute: Accepts and returns Compose-specific element attributes. See [Compose Element Attributes](#compose-element-attributes) for the full list of supported Compose element attributes.
 - getElementScreenshot: Fetches a screenshot of the given Compose element. Available since driver version *2.14.0*
-- `mobile: swipe`: Performs swipe gesture on the given element in the given direction. 
+- `mobile: swipe`: Performs swipe gesture on the given element in the given direction.
 The `swiper` argument is not supported in Compose mode. Available since driver version *2.15.0*
 
 Calling other driver element-specific APIs not listed above would most likely throw an exception as Compose and Espresso elements are being stored in completely separated internal caches and must not be mixed.