Make it work with devices/emulators

[takahirom]

I don't know if I do this or not, but We should be able to test both the JVM and the emulator/device using the same test with the following steps using AndroidJUnit4.

• Create Gradle task for AndroidTest
• Sending and receiving images via adb. Before the test starts, push the image that is currently stored to the device for verify. And pull the results when the test is over.
• Creation of roborazzi-android-painter and roborazzi-awt-painter. We need to abstract the painter. We need to be able to draw to Android Bitmap what we are doing now with BufferedImage.

[sergio-sastre]

I can help with this at some point in the future, but I believe it does not have high prio.

One can always use another library for on-device screenshot testing when needed (as we do 😅)

However, when implementing this, I’d suggest to do something similar to Dropshots. It runs with the connectedAndroidTest tasks, what comes together with support for Gradle managed devices, which other libraries don’t support

[utzcoz]

@sergio-sastre @takahirom I think you can check ActivityScenario, which is cross-environments from Robolectric to Devices. There are two important keys that it can work like this:

1. AndroidX Test's AndroidJUnit4 will dispatch the runner to RobolectricTestRunner if it finds Robolectric class when running. Otherwise it will use default AndroidX Test runner to run tests on devices.'
2. Robolectric supports necessary APIs that ActivityScenario requires to support these APIs in Robolectric environment.

Maybe Robarazzi can do similar work to make itself cross-environments with the only one top-level API suite.