Speed up unit tests

[Femimat]

Contributor checklist

• This pull request is on a separate branch and not the main branch
• I have tested my code with the ./gradlew lintKotlin detekt test command as directed in the testing section of the contributing guide

---

Description

1. Matrix Strategy: I added a matrix strategy to parallelize the tests for the Conjugate and Keyboards flavors. This allows both sets of tests to run at the same time on different runners.
2. Pre-building APKs: I added a Pre-build Android Test APKs step that runs before the emulator starts. This prevents the build process from competing for resources with the emulator, which can lead to timeouts and slower test execution.
3. Removed redundant delays: I removed the sleep 30 and sleep 10 commands, as android-emulator-runner handles waiting for the device. I also removed redundant animation settings that are already handled by the disable-animations: true flag.
4. Workflow Cleanup:

• Renamed the "Run Ktlint" step in the test job to "Run Unit Tests" to accurately reflect that it runs ./gradlew test.

• Adjusted timeout-minutes to a more appropriate 45 minutes per parallel job.

• Investigate and speed up Android instrumentation tests #580

[github-actions]

Thank you for the pull request! 💙🩵

The Scribe-Android team will do our best to address your contribution as soon as we can. The following are some important points:

• Those interested in developing their skills and expanding their role in the community should read the mentorship and growth section of the contribution guide
• If you're not already a member of our public Matrix community, please consider joining!
  • We'd suggest that you use the Element client as well as Element X for a mobile app
  • Join the General and Android rooms once you're in
• Also consider attending our bi-weekly Saturday developer syncs!
  • Details are shared in the General room on Matrix each Wednesday before the sync
  • It would be great to meet you 😊

Note

Scribe uses Conventional Comments in reviews to make sure that communication is as clear as possible.

[github-actions]

Maintainer Checklist

The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

• Tests for changes have been written and the unit test, linting and formatting workflows within the PR checks do not indicate new errors in the files changed

  • Tests may need to be reran as they're at times not deterministic

• The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[andrewtavis]

Can you take a look at the merge conflicts, @Femimat? Let us know when this is ready for a review :)

[Femimat]

Hi @andrewtavis, thanks for the heads up! I’m currently working on resolving the merge conflicts and will let you know once it’s ready for review.

[Femimat]

Hi @andrewtavis, you can review the PR now.

[andrewtavis]

Sounds good, @Femimat! Thanks for resolving the conflicts 😊

[DeleMike]

LGTM too. Can you share with me the time it takes now?

Earlier, the instrumentation tests usually took between 12 to 15 minutes

[Femimat]

Hi @DeleMike, The tests now run in parallel: Conjugate took 7m and Keyboards took 13m. This brings the total wall-clock time down to 13 minutes, while providing much faster feedback for the first flavor.

ci_android / build app (pull_request)
ci_android / build app (pull_request)Successful in 4m
ci_android / collect_coverage (pull_request)
ci_android / collect_coverage (pull_request)Successful in 5m
ci_android / Run Android Instrumentation Tests (Conjugate) (pull_request)
ci_android / Run Android Instrumentation Tests (Conjugate) (pull_request)Successful in 7m
ci_android / Run Android Instrumentation Tests (Keyboards) (pull_request)
ci_android / Run Android Instrumentation Tests (Keyboards) (pull_request)Successful in 13m
ci_android / Run Ktlint and Detekt (pull_request)
ci_android / Run Ktlint and Detekt (pull_request)Successful in 1m
ci_android / Run Tests (pull_request)
ci_android / Run Tests (pull_request)Successful in 5m

[DeleMike]

Thank you so much @Femimat!

I understand there may be minor factors affecting the speed of these tests. However, I feel like an average of 10-12 minutes is fair.

Actually, when you physically do an instrumentation test, they take around the same time, if not longer.

Unless someone has other ideas, everything looks good here.
@angrezichatterbox, what do you think?

cc: @andrewtavis