Hello, question regarding `expect/actual` if the recommendation is to use interfaces instead of an e...

# touchlab-tools

[Jemo]

Hello, question regarding expect/actual
if the recommendation is to use interfaces instead of an expect/actual, then how do you write tests for that common classes?

example:

interface UUIDProvider {
   fun randomUID(): String
}

@Test
fun randomUID_isNotEmpty() {
    assertTrue(UUIDProvider().randomUID().isNotEmpty()) // we can't do that.
}

[Jemo]

In that case we are forced to create UUIDProvider using Di right?

[kpgalligan]

Use interfaces instead of expect/actual for classes. In this case, if you didn't want to deal with DI, I'd suggest writing expect/actual factory functions to create the platform-specific interface implementation. expect/actual factory functions are also useful in main code for default implementations, while still allowing for injected ones. In that scenario, just remember to make those factory functions internal 🙂