@syntaxerror247 To complete the integration, we'll need to set up the CI to automatically run the integrated tests. Can you look into what it'd take to make this happen.

This blogpost seems like a good reference to start with: https://medium.com/@peterkagure/running-instrumented-tests-on-github-actions-with-firebase-test-lab-ac17bb36ae9c

@m4gr3d I just noticed that there's errors in Logcat while running the instrumented tests, and it seems the tests aren’t running.

Error1: App doesn't auto-launch; I have to launch it manually from launcher.

I checked out the branch on a new machine, and I'm able to run and replicate the test results, so it may be an issue with how you ran the tests. I've updated the description with some instructions for how to run from Android Studio. Can you give it a try and see if that works.

Error2:

ERROR: Couldn't load file 'res://project.binary', error code 19.
    at: _load_settings_text_or_binary (core/config/project_settings.cpp:920)

That's expected. A Godot project can either be loaded from project.godot or project.binary (binary version of the human readable version), but the engine always tries the binary version first, and shows this error when it doesn't find it before falling back to the human readable version.
The instrumented tests use the human readable verison (project.godot, with the project under platform/android/java/app/src/instrumented/assets) so you'll see this error every time they run.

Error3:

ERROR: Variant is too deep! Bailing.
    at: _variant_to_jvalue (platform/android/jni_utils.cpp:93)
    GDScript backtrace (most recent call first):
           [0] test_variant_conversion_safe_from_stack_overflow (res://test/javaclasswrapper/java_class_wrapper_tests.gd:136)
           [1] __exec_test (res://test/base_test.gd:12)
           [2] run_tests (res://test/javaclasswrapper/java_class_wrapper_tests.gd:17)
           [3] _launch_tests (res://main.gd:22)

Also expected. The failing condition is the test crashing with a stack overflow error as described here.
The passing condition is the test not crashing and this error being logged.
This test validates the fix added in #110452.

I'm running with ./gradlew connectedInstrumentedDebugAndroidTest -Pperform_signing=true Also tried with Android Studio but same errors.

@m4gr3d I just noticed that there's errors in Logcat while running the instrumented tests, and it seems the tests aren’t running.
Error1: App doesn't auto-launch; I have to launch it manually from launcher.

I checked out the branch on a new machine, and I'm able to run and replicate the test results, so it may be an issue with how you ran the tests. I've updated the description with some instructions for how to run from Android Studio. Can you give it a try and see if that works.

Already tried with Android Studio as well, followed the same steps, but the app doesn’t auto-launch. The test run is stuck until I manually open the app, after which it proceeds and completes.

Tested with an emulator, it works as expected there. Seems like the issue is with my device then :/

Thanks!