Comments (13)
For completeness, please share the full stack trace of IllegalAccessError(s)
you're seeing when trying with the unbundled setup.
Original comment by [email protected]
on 14 Jan 2014 at 7:42
- Changed state: Accepted
from android-test-kit.
Please update Espresso to work with Dagger 1.2.
Original comment by [email protected]
on 21 Jan 2014 at 1:44
from android-test-kit.
here is the stacktrace and it shows what's the problem. There seems to be some
internal changes in dagger that made it incompatible with 1.1 builds:
01-21 09:58:13.143: I/TestRunner(2923): failed:
testEnterSomeValues(com.groupon.merchant.redemption.RedeemActivityTest)
01-21 09:58:13.143: I/TestRunner(2923): ----- begin exception -----
01-21 09:58:13.143: I/TestRunner(2923): java.lang.NoSuchMethodError:
dagger.internal.ModuleAdapter.<init>
01-21 09:58:13.143: I/TestRunner(2923): at
com.google.android.apps.common.testing.ui.espresso.GraphHolder$EspressoModule$$M
oduleAdapter.<init>(GraphHolder$EspressoModule$$ModuleAdapter.java:17)
01-21 09:58:13.143: I/TestRunner(2923): at
java.lang.Class.newInstanceImpl(Native Method)
01-21 09:58:13.143: I/TestRunner(2923): at
java.lang.Class.newInstance(Class.java:1130)
01-21 09:58:13.143: I/TestRunner(2923): at
dagger.internal.Loader.instantiate(Loader.java:84)
01-21 09:58:13.143: I/TestRunner(2923): at
dagger.internal.FailoverLoader$1.create(FailoverLoader.java:42)
01-21 09:58:13.143: I/TestRunner(2923): at
dagger.internal.FailoverLoader$1.create(FailoverLoader.java:40)
01-21 09:58:13.143: I/TestRunner(2923): at
dagger.internal.Memoizer.get(Memoizer.java:56)
01-21 09:58:13.143: I/TestRunner(2923): at
dagger.internal.FailoverLoader.getModuleAdapter(FailoverLoader.java:57)
01-21 09:58:13.143: I/TestRunner(2923): at
dagger.internal.Modules.loadModules(Modules.java:40)
01-21 09:58:13.143: I/TestRunner(2923): at
dagger.ObjectGraph$DaggerObjectGraph.makeGraph(ObjectGraph.java:166)
01-21 09:58:13.143: I/TestRunner(2923): at
dagger.ObjectGraph$DaggerObjectGraph.access$000(ObjectGraph.java:135)
01-21 09:58:13.143: I/TestRunner(2923): at
dagger.ObjectGraph.create(ObjectGraph.java:127)
01-21 09:58:13.143: I/TestRunner(2923): at
com.google.android.apps.common.testing.ui.espresso.GraphHolder.graph(GraphHolder
.java:32)
01-21 09:58:13.143: I/TestRunner(2923): at
com.google.android.apps.common.testing.ui.espresso.Espresso.espressoGraph(Espres
so.java:36)
01-21 09:58:13.143: I/TestRunner(2923): at
com.google.android.apps.common.testing.ui.espresso.Espresso.onView(Espresso.java
:51)
01-21 09:58:13.143: I/TestRunner(2923): at
com.groupon.merchant.redemption.RedeemActivityTest.testEnterSomeValues(RedeemAct
ivityTest.java:18)
01-21 09:58:13.143: I/TestRunner(2923): at
java.lang.reflect.Method.invokeNative(Native Method)
01-21 09:58:13.143: I/TestRunner(2923): at
java.lang.reflect.Method.invoke(Method.java:525)
01-21 09:58:13.143: I/TestRunner(2923): at
android.test.InstrumentationTestCase.runMethod(InstrumentationTestCase.java:214)
01-21 09:58:13.143: I/TestRunner(2923): at
android.test.InstrumentationTestCase.runTest(InstrumentationTestCase.java:199)
01-21 09:58:13.143: I/TestRunner(2923): at
android.test.ActivityInstrumentationTestCase2.runTest(ActivityInstrumentationTes
tCase2.java:192)
01-21 09:58:13.143: I/TestRunner(2923): at
junit.framework.TestCase.runBare(TestCase.java:134)
01-21 09:58:13.143: I/TestRunner(2923): at
junit.framework.TestResult$1.protect(TestResult.java:115)
01-21 09:58:13.143: I/TestRunner(2923): at
junit.framework.TestResult.runProtected(TestResult.java:133)
01-21 09:58:13.143: I/TestRunner(2923): at
junit.framework.TestResult.run(TestResult.java:118)
01-21 09:58:13.143: I/TestRunner(2923): at
junit.framework.TestCase.run(TestCase.java:124)
01-21 09:58:13.143: I/TestRunner(2923): at
android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:191)
01-21 09:58:13.143: I/TestRunner(2923): at
android.test.AndroidTestRunner.runTest(AndroidTestRunner.java:176)
01-21 09:58:13.143: I/TestRunner(2923): at
android.test.InstrumentationTestRunner.onStart(InstrumentationTestRunner.java:55
4)
01-21 09:58:13.143: I/TestRunner(2923): at
com.google.android.apps.common.testing.testrunner.GoogleInstrumentationTestRunne
r.onStart(GoogleInstrumentationTestRunner.java:167)
01-21 09:58:13.143: I/TestRunner(2923): at
android.app.Instrumentation$InstrumentationThread.run(Instrumentation.java:1701)
01-21 09:58:13.143: I/TestRunner(2923): ----- end exception -----
01-21 09:58:13.143: I/TestRunner(2923): finished:
testEnterSomeValues(com.groupon.merchant.redemption.RedeemActivityTest)
Original comment by [email protected]
on 21 Jan 2014 at 10:06
from android-test-kit.
Is it possible to get an ETA of this? Thanks.
Original comment by [email protected]
on 27 Feb 2014 at 11:51
from android-test-kit.
Any news about ETA? Thnaks!
Original comment by [email protected]
on 19 Mar 2014 at 3:22
from android-test-kit.
I'd like to point out that this :
https://github.com/JakeWharton/double-espresso works with gradle for us. With
dagger 1.2 and no extra hacks.
Original comment by [email protected]
on 19 Mar 2014 at 5:59
from android-test-kit.
Anyone has a workaround for this?
Original comment by [email protected]
on 24 Apr 2014 at 11:25
from android-test-kit.
https://github.com/JakeWharton/double-espresso :)
Original comment by [email protected]
on 25 Apr 2014 at 6:42
from android-test-kit.
For those that want Espresso and Robolectric, Jake Wharton's double-espresso
does not work. So I recompiled the current master of espresso against Dagger
1.2.1 and published the Maven-ready artifacts here:
https://github.com/tommyd3mdi/mvn
Original comment by [email protected]
on 5 Jun 2014 at 1:48
from android-test-kit.
This (https://github.com/tommyd3mdi/mvn) isn't working for me. Attempting to
access https://raw.githubusercontent.com/tommyd3mdi/mvn/master results in a 400
error.
Double-espresso isn't working for me. I'm not able to exclude Espresso tests
from my Robolectric run and thus compilation errors ensue.
Original comment by [email protected]
on 6 Oct 2014 at 6:04
from android-test-kit.
@gloe...
The latter is the maven repository URL, there is no whatsoever directory index
page expected. Just add it as additional repository location as stated on the
project page.
Original comment by [email protected]
on 7 Oct 2014 at 8:05
from android-test-kit.
Hm... I'll have to take another look. I thought I followed the instructions,
and it didn't work. AS said it couldn't find the lib. Very possible I had
something else going on.
Original comment by [email protected]
on 7 Oct 2014 at 12:52
from android-test-kit.
Fixed in Espresso 2.0
Original comment by [email protected]
on 20 Dec 2014 at 4:33
- Changed state: Fixed
from android-test-kit.
Related Issues (20)
- Performing click on fullscreen does not work (Fullscreen Activity Code Template) HOT 4
- Test failing on Lollipop when performing a click on a view whose parent layout has an indeterminate progress bar HOT 2
- Prebuilt binaries provide/use inconsistent versions of Dagger HOT 3
- getting "Espresso ViewAssertion Failed Looped for 3528 iterations over 60 SECONDS. The following Idle Conditions failed ." error HOT 1
- openActionBarOverflowOrOptionsMenu does not work with non-english locale & proguard used HOT 1
- Unable to run espresso tests - ComponentInfo not found for android.support.test.runner.AndroidJUnitRunner HOT 2
- AndroidJUnitRunner now marking failures where before it had not HOT 1
- DrawerActions is (still) leaking the parent listener HOT 3
- Context not initialized with ProviderTestCase2 (NullPointerException) HOT 1
- Basic intent test fails. HOT 1
- Using recyclerview-v7:22.1.1 causes NPEs with espresso-contrib 2.1 because it depends on recyclerview-v7:22.0.0 HOT 1
- Using onData with an overlaid View won't properly click on items
- Getting DexException when running assembleDebugAndroidTest goal second time HOT 4
- Enhancement: FlakyTest for JUnit4/Espresso HOT 2
- MonitoringInstrumentation leaking activity instances through ExecutorService HOT 3
- withText doesn't find views with textAllCaps attribute used HOT 1
- using onData in RecyclerView HOT 4
- Espresso-contrib cannot inflate RecyclerView with IllegalStateException (Unable to find LayoutManager) HOT 5
- Provide API to list tests that will be run
- Add API for adding RunListeners to AndroidJUnitRunner
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from android-test-kit.