-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Problems on Android using Jest test runner #362
Comments
Any new updates on this issue?
Thanks |
@coderjonny I am trying with exact same config. Were you able to setup ReactNative+Detox+Jest for Android? |
@anupamsmaurya @coderjonny @SMJ93 Any update on this issue? |
@anupamsmaurya @prasanth95 yes, I was able to get it up and running on both iOS and Android with detox 6.0.2 and Jest 21.2.1. |
@SMJ93 For me detox is unable to create app-debug-androidTest.apk can you suggest anything on this stacloverflow post https://stackoverflow.com/questions/48148064/referenceerror-device-is-not-defined-when-using-detoxjest-in-react-native-fo |
@anupamsmaurya Looks like your config may be incorrect. Do the example detox examples work for you? This is what we have in our package.json:
And the following Detox config:
Hope this helps! |
Description
We have switched test runners from Mocha to Jest using the instruction guide here, but there seem to be a few issues:
With mocha we would add the flag for this to be enabled:
--loglevel verbose
When printing the instrumentation there is no bundle ID for the app we want to test - this used to show with mocha:
adb shell pm list instrumentation
Looking at the log in detox it doesn't seem to install the apk's onto the device before calling the .
There seems to be an issue installing both the Android app apk
com.appname
and the test apkcom.appname.test
when using Jest which then results in the following error:Steps to Reproduce
Use Jest as the test runner instead of Mocha on Android by following this guide.
Detox, Node, Device, Xcode and macOS Versions
Here is the detox and jest config in the package.json
The text was updated successfully, but these errors were encountered: