Fixed
Status Update
No update yet.
Comments
sl...@google.com
Agreed, the reason for the Runner 1.0.0 dependency is because of Espresso Remote (Multi Process Support), which depends on instrumentation connection in Runner. We were looking into breaking apart this dependency, but couldn't get it done for this release.
ar...@gmail.com
Alright, great that you know about the problem!
Feel free to discuss proposals here if you want some feedback from outside community :)
Feel free to discuss proposals here if you want some feedback from outside community :)
sl...@google.com
sl...@google.com
nk...@google.com
It's not trivial to completely decouple the dep of Espresso on Runner. However, as Stephan mentioned above we successfully decoupled Espresso Remote (Multi Process Support) from Espresso Core which in turn makes Espresso's dep on Runner very light and more importantly backwards compatible.
Closing this bug as Fixed, expect these changes in the next Espresso release.
Closing this bug as Fixed, expect these changes in the next Espresso release.
ar...@gmail.com
I think it's ok if you'll depend on Runner as an optional runtime dependency to do something better by default, but if Espresso won't work with other test runners — that's pretty bad.
nk...@google.com
I agree with you, unfortunately that dependency was there since early versions of Espresso and most other custom runners extend from our AndroidJUnitRunner.
With that said, we do have a greater effort of refactoring and decoupling everything out, stay tuned.
With that said, we do have a greater effort of refactoring and decoupling everything out, stay tuned.
lu...@gmail.com
Esthela Hernández RodrÃguez
Description
What steps will reproduce the problem?
1. Update Espresso from 2.x to 3.0.0
2. Don't update `com.android.support.test.runner` from 0.5 to 1.0 because it's not working out of the box.
3. Observe that build fails because Espresso 3.0.0 can not be used with Test Runner 0.5 (unless you start hacking build process to force that)
How are you running your tests (via Android Studio, Gradle, adb, etc.)?
./gradlew connectedAndroidTest, Composer (
What is the expected output? What do you see instead?
Espresso should NOT depend on test runner. It's just a UI test library. It should not matter what test runner you use with Espresso.
It's like if AsserJ would depend on JUnit.