I find instrumented test on GH actions is finicky in my own personal
experience, but still it probably would be ideal to include it. Tbh I
thought it was already included but alas it seems to only run the unit
tests.
Maybe the instrumented tests can be its own workflow so that it's
independent from the quicker unit tests? That way if it ends up
failing/timing out it can be reran independently as well.
On 2026-10-29 2:27 p.m., Manuel Beck wrote:
Hi Cordova community,
while fixing a double back button event on Android 16
(https://github.com/apache/cordova-android/pull/2029), I noticed that
instrumentation tests exists, but that the GitHub Actions workflows do not
build or execute them, just JavaScript and Java unit tests. Also the
instrumentation tests were outdated and had several build and runtime failures
which I fixed in some PRs.
On our plugin side, automated tests are run on Android emulators in GitHub
Actions, using android-emulator-runner together with Cordova Paramedic.
Could we add a GitHub Actions workflow using android-emulator-runner, as our
plugin repositories already do, and execute cordova-android’s instrumentation
suite with Gradle’s connectedDebugAndroidTest task? Paramedic would not be
required for these tests.
Do we want to excecute the instrumentation tests at all? I would say, that it
is also good for cordova-android to run tests on an emulator.
Regards,
Manuel
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
