It's almost 2020 and it remains a challenge to run Android Instrumented tests on CI, especially for opensource projects and small teams:
Setting ...
For further actions, you may consider blocking this person and/or reporting abuse
Hi! Thanks for such deep tutorial. It's helpful for beginners in CI like me
What do you think, is there any other way to write tests for Room's Dao classes? Actually I don't have any other instrumented tests for now.
Thanks!
You mean running those DAO tests as regular unit tests that can be run on the host machine without an emulator / real device?
You could try Robolectric, or look at sqldelight which supports using an in memory Sql driver for unit tests. Here’s an example.
Hope that helps!
Thanks for the insight!
Was wondering, is there a way to specify a different emulator port when using
reactivecircus/android-emulator-runner@v2? I keep gettingerror: could not connect to TCP port 5554: Connection refusedwhen running my job in a self-hosted runner.This works perfectly fine on macos-latest but my repo is private and I'm trying to minimise my costs.
Hey. Thanks a lot. This really helped me to setup instrumented tests on my project, which is all about tests in Espresso and XCUITest. And yeah, it works great with GitHub Actions: github.com/michallaskowski/kuiks/p...
Glad it helped!
By the way I also wrote a ui testing library based on espresso. Feel free to take whatever you may find useful for your KMP project.
@ychescale9 When running on a self-hosted
macOSrunner that has M1 chip, what setup changes we have to do?