Add instrumentation test job to android_ci.yml

[DeleMike]

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

Resolves #422

This PR adds a new instrumentation_test job to .github/workflows/android_ci.yml to run instrumentation tests using ./gradlew connectedAndroidTest.

Testing:

• Ran ./gradlew connectedAndroidTest locally to confirm tests pass.
• Verified test reports in app/build/reports/androidTests/connected/.

Notes:

• Assumed tests exist in app/src/androidTest.

• closes Add Instrumentation Tests to GitHub Actions Workflow #422

[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. If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Android rooms once you're in. Also consider attending our bi-weekly Saturday dev syncs. It'd be great to meet you 😊

[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 :)

• The linting and formatting workflows within the PR checks do not indicate new errors in the files changed

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

[DeleMike]

Hello @angrezichatterbox , I have a PR here to add GH Actions for android instrumented tests.

for now, only the license check action is running!

Can you please help me check/verify that is PR is valid?

cc: @andrewtavis

[DeleMike]

Hi @angrezichatterbox , so I fixed the issue. It was a typo issue and improper referencing.

I await your feedback now.

cc: @andrewtavis

[DeleMike]

Hi @angrezichatterbox, so I fixed another case where the Emulator fails to start. This was causing the test cases to fail after I merged main into this branch. If you need any explanation on my script, please ask, I will answer appropriately.

cc: @andrewtavis

[angrezichatterbox]

Let me try running this workflow using act locally and would sent in the review later today :)

[angrezichatterbox]

Looks good to me @DeleMike. You tried running it by creating a PR for yourself in your fork right. I couldn't run using act due to permission issue but looks fine.

[DeleMike]

Yes, I did. And it worked well! :)

Wanted you to confirm that this is what you expected.

[andrewtavis]

My commit was minor edits to standardize the names of the stages here :) Thanks so much for the quick work here, @DeleMike! 😊😊

[DeleMike]

Oh thank you! ☺️
Most likely my IDE settings.