Unit Tests - Android + Kotlin

[mvarendorff]

What does this PR do?

This PR adds generated unit tests to Android and Kotlin SDKs. It also contains some refactoring to generate similar classes from the same template to both the Android and Kotlin SDK, similar to how Dart and Flutter share templates.

Test Plan

I set up the generated project locally and ran the respective test command (./gradlew library:test for the Android SDK (requires Java 8-11 not higher!) and ./gradlew test for the Kotlin SDK)

Related PRs and Issues

• 🚀 Feature: Unit Tests #680

Have you read the Contributing Guidelines on issues?

Yup

---

Discord username for swag as requested by Tessa: yestheory

[loks0n]

Awesome PR 😃

[mvarendorff]

Converting this to a draft for the time being until I figure out what gradle version still works with Java 8 to get the pipeline green. Not sure when I will get to it since I am uncertain how long setting up the build locally for proper testing will take.

[mvarendorff]

After lots of battling, I found 2 culprits that were causing issues with tests:

1. The latest Android Gradle build plugin supporting Java 8 is 4.2.2; anything beyond that needs at least Java 11. For some reason tests fail for me locally on Java 17+ but run fine with Java 11, see https://stackoverflow.com/a/76170361/6707985. I downgraded back to 4.2.2 to get the pipeline to work and added a note to the original PR post noting the restriction to Java 11.

2. Robolectric runs a compatibility check on startup; for Android 29+ this will fail with the error that creating a Robolectric Sandbox for the respective Android API version requires at least Java 9. I removed Robolectric and mocked out the parts of the SDK that were needed using different snippets I found around the internet. When Java 8 is dropped longterm, the implementation using robolectric that was present at 6b86cbf should work properly and be a bit more sensible. I have no idea what part of this PR caused issues with the existing robolectric test, to be honest...

---

I have no idea why node is failing now; this is cruel but I am relatively confident that's not my fault because I didn't touch node.

[loks0n]

I have no idea why node is failing now; this is cruel but I am relatively confident that's not my fault because I didn't touch node.

This is fixed on the 1.5.x branch now, you may rebase to this if you want to see everything pass

[mvarendorff]

Ah, I see! I will hold off on that I until that's merged I think to avoid more chaos than necessary. As long as I know it was not my fault indeed and it's fixed somewhere else I got peace of mind! Thanks :)