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.
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
Unable to use fork to run instrumentation tests #88
Comments
Hi, I remember that method changing in more recent versions of ddmlib. What I suspect is happening, is that you're using a version of the Android Gradle plugin that brings an older version, which doesn't have that method. Are you using pre-2.0.0 by any chance? If my guess is not correct, what would help is a project that reproduces the issue. |
Thanks for your quick response. Sorry, i could not get a chance to reply to your message earlier. Yes, we were using 1.2.3 and i upgraded it to 2.0.0. However, am now seeing the following issue after i added build script dependency and fork gradle plugin in build.gradle file. Can you please provide your inputs on how i can get this resolved? Test-Machine:Test-Project pagarw200$ ./gradlew clean FAILURE: Build failed with an exception.
|
The name of the plugin is |
Thanks. That helped. Another new issue i see now is that fork detects emulators but it is not running any tests. Any suggestions on what am i missing here? I tried running following command after having 3 emulators up and running: Here is the debug logs of error - 16:28:39.053 [QUIET] [system.out] done |
Not sure, but if you can send me a sample project that reproduces this issue I can have a look. |
Hi,
I am really looking forward to use this library for my project as am hoping this library would reduce the execution time of our tests on CI server.
I have added the latest fork plugin (classpath 'com.shazam.fork:fork-gradle-plugin:1.3.0') in build.gradle and tried running the tests, i saw the error "Error when trying to scan for test classes
com.shazam.fork.suite.NoTestClassesFoundException: No tests classes were found in the dex files.". This got resolved by adding testPackage name as you suggested in #61.
When i made second attempt to run the tests, i got following error:
"Exception in thread "DeviceExecutor-0" java.lang.NoSuchMethodError: com.android.ddmlib.IDevice.installPackage(Ljava/lang/String;Z[Ljava/lang/String;)V
at com.shazam.fork.system.adb.Installer$1.run(Installer.java:53)
at com.shazam.fork.system.adb.Installer.tryThrice(Installer.java:77)
at com.shazam.fork.system.adb.Installer.reinstall(Installer.java:47)
at com.shazam.fork.system.adb.Installer.prepareInstallation(Installer.java:41)
at com.shazam.fork.runner.DeviceTestRunner.run(DeviceTestRunner.java:61)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
done"
As per the following issue(#66) you closed in github for this project, this issue was fixed in fork 1.2.0 but i still see it though am using fork 1.3.0 :( I have tried 1.2.0 as well but still no luck.
It would be great if you can suggest if am missing something here.
Please advice on how i can get the above issue fixed and get the instrumentation tests running using fork.
The text was updated successfully, but these errors were encountered: