robolectric VS Kaspresso

Robolectric

Do you use Robolectric to test string resolving?

@Config(instrumentedPackages = ["androidx.loader.content"]) is a workaround for https://github.com/robolectric/robolectric/issues/6593

There is also an issue with Robolectric which can be worked around by adding @Config(instrumentedPackages = ["androidx.loader.content"]) annotation to the test class.

If it's failing only on robo, this might be the cause: https://github.com/robolectric/robolectric/issues/6411

Unit tests. ~X0,000. These run on the jvm (not Android), via http://robolectric.org/

Take a look at http://robolectric.org. It has a specific JUnitRunner class for running unit tests in the test package with shadow classes for Android objects like application context. It is broadly used and there are a lot of examples on github and robolectric provides several themselves

https://github.com/KasperskyLab/Kaspresso if you really need to do it then this how you should do it, though I believe integration tests are inherently flawed

espresso is Google's general recommendation, but there are other tools out there that exist like appium or kaspresso. Sure there are more, just goigle it to see what else there is.

Read additional information here.

All detailed information is here - https://github.com/KasperskyLab/Kaspresso/releases/tag/v1.3.0

Have a look at Kaspresso

Hi everyone! If you are at the beginning of creating the writing autotests process and looking for the appropriate tool then you are welcome to read the full comparison of existing tools. Article 1 and Article 2 describe such frameworks as Espresso, UI Automator, Appium, Barista, Kaspresso and try to infer the best suitable framework basing on your demands.