Skip to content

docs: address no compose deps branch #880

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Aug 7, 2023
Merged

docs: address no compose deps branch #880

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
9450d64
docs: address no compose deps branch
KazuCocoa May 17, 2023
41480b2
Update README.md
KazuCocoa Aug 6, 2023
002c376
Update README.md
KazuCocoa Aug 7, 2023
95bbebb
Update README.md
KazuCocoa Aug 7, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,10 @@ The Espresso package consists of two main parts:
The key difference between [UiAutomator2 Driver](https://github.com/appium/appium-uiautomator2-driver) and Espresso Driver is that UiAutomator2 is a black-box testing framework, and Espresso is a "grey-box" testing framework. The Espresso Driver itself is black-box (no internals of the code are exposed to the tester), but the Espresso framework itself has access to the internals of Android applications. This distinction has a few notable benefits. It can find elements that aren't rendered on the screen, it can identify elements by the Android View Tag and it makes use of [IdlingResource](https://developer.android.com/reference/android/support/test/espresso/IdlingResource) which blocks the framework from running commands until the UI thread is free. There is limited support to automate out of app areas using the mobile command [uiautomator](https://github.com/appium/appium-espresso-driver/blob/b2b0883ab088a131a47d88f6aeddd8ff5882087d/lib/commands/general.js#L188)


## Jetpack compose dependencies
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we move it under troubleshooting section?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, it makes sense


Espresso driver has Jetpack Compose dependencies to [support Jetpack Compose](#jetpack-compose-support). It could break the application under test's dependencies. The typical case is when the application under test does not have the Jetpack Compose dependencies. Then. you can try out [no compose dependencies branch](https://github.com/appium/appium-espresso-driver/pull/879)). In Appium 2.0, the branch is available as `appium driver install --source=local /path/to/the/appium-espress-driver` with the `no-compose-deps` branch instead of npm installation.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

extra dot after Then

I am also not very convinced about the branch usage. This statement assumes we are going to keep this branch up to date with master, which is, probably, not going to happen?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yea, need to maintain #879

I met various error mesasges like androidx related dependencies issue when espresso server launches. I was not able to resolve by modifying the existing gradle like adding exclude. Probably some of compose dependencies caused that. (It is not happy to keep this for me actually, but keep modifying gradle file was harder than just remove compose dependencies)

I'm ok to keep #879 as a hidden usage (i'll keep it as my best) to keep espresso driver availability for non-compose users


## Requirements

On top of standard Appium requirements Espresso driver also expects the following prerequisites:
Expand Down