Skip to content

Run CI tests against multiple Android versions #415

@jkuester

Description

@jkuester

Good first issue

This ticket has the Good first issue label! This means it's been especially curated by other CHT contributors to be easy to work on for first time contributors per the docs.

Overview

Describe the issue
CHT Android 1.0+ supports running on devices with Android 5.0+.

However, our GitHub Action CI jobs are only running tests against one Android version (currently Android 14 (level 34)).

Describe the improvement you'd like

It looks like reactivecircus/android-emulator-runner supports all the way back to Android 4 (level 14), so hopefully we can dial it in to test with Android 5 (level 21) and Android 16 (level 36).

Describe alternatives you've considered

We have discussed raising the minimum supported version of Android in a 2.x release of cht-android. I think that conversation will be influenced by whatever level of Android we are able to successfully get automated testing on. If we can run our tests on Android 5 and all our dependencies continue to support it, then there is not really any reason to bump our minimum supported version.

Details

Update the instrumentation-tests job in the GitHub CI workflow to use a matrix strategy that adjusts the reactivecircus/android-emulator-runner api-level property to 21 or 36.

We might have to iterate on the changes several times depending on how things run when the PR is opened, but hopefully we can find a configuration that works.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Good First IssueGood for first time contributionsType: Technical issueImprove something that users won't notice

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions