Setting up tests #4572
Replies: 2 comments 6 replies
-
|
If you run the test using the CLI in a local terminal, does it work? I think the command in your case would be: ./gradlew -Pandroid.testInstrumentationRunnerArguments.class=org.oppia.android.app.administratorcontrols.AdministratorControlsActivityTest :app:connectedAndroidTestAlso, have you checked the logcat logs on your device/emulator after starting the test? It may be the case that the app is misbehaving. While google/dagger#3223 was caused by something that couldn't break for us, it's noteworthy because the issue illustrated there might also affect us (specifically the fact that we use a custom runner which might not be playing nicely with the latest Android Studio or AGP version). Edit: Sometimes this issue can come up if the app fails to start (or, in your case, install). You can force a clean state by manually uninstalling the app via the system's app package manager, or via ADB on the CLI using: adb uninstall org.oppia.android |
Beta Was this translation helpful? Give feedback.
-
|
@mbobiosio I think you have to downgrade your Android Studio to Bumblebee to run the tests on that or check this disscusion here you able to find the solution. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have followed the recommendations on this discussion but it doesn't solve my issue.
Android Studio runs the build process successfully, shows "Test Passed" but no test in particular indicated. The app is not started on the device (emulator and mobile phone) during this process.
The expected output

Android Studio version: Android Studio Arctic Fox | 2020.3.1
Java version: Java 8
OS: Ubuntu 22.04.1 LTS
Beta Was this translation helpful? Give feedback.
All reactions