Might I ask how you guys use a logging framework in code that has to be unit tested? Standard Androi...

# android

[Daniel]

Might I ask how you guys use a logging framework in code that has to be unit tested? Standard Android Log. provokes the not mocked exception.

[mg6maciej]

ferranis: I do something like this: https://github.com/mg6maciej/fluffy-octo-rotary-phone/blob/develop/app/src/main/java/pl/mg6/likeornot/infrastructure/logger/ErrorLogger.kt

[Daniel]

Just for clarification: Its a singleton and you can switch out the logging function if necessary? So before each test you would do that and in production code it defaults to the firebase implementation?

[mg6maciej]

Yes, although this is more for functional tests.

[Daniel]

That's very smart! Thank you for sharing that!

[mg6maciej]

Works with everything really. Retrofit interfaces, GPS or even facebook login button (if you wrap your head around how to create a provider for that).

[mg6maciej]

For unit tests I'd recommend natural dependency inversion tho.

[mg6maciej]

I rarely log stuff, but for testing analytics events calls are made, it's good.

[Daniel]

Its just amazing what you can do with functions in kotlin, storing a function in a property is just so science fiction if you come from java 6.

And for logging: the same. Since I learned automated testing there is no need for it in my app - but the use case for logging mght arise somewhere. So its good to know (thank you for that!)

[lekz112]

In my case, I use slf4j + timber for app, simplelogger for unittests.
While you can inject logger, with slf4j you usually use static factory method:

companion object {
        private val logger = LoggerFactory.getLogger(BaseActivity::class.java.simpleName)
    }

After that it can be used as usual:

logger.debug("onCreate() called with: savedInstanceState = [{}]", savedInstanceState)