Dmitry Zhukov

Hey! I've faced the same issue in app module. Module configuration is ``` extensions.configure { applicationPackageId = "ru.myapp.feature.codeinput" testPackageId = "ru.myapp.feature.codeinput.test" } android { resourcePrefix = "codeinput_" namespace = "ru.myapp.feature.codeinput"...

Any updates? I have the same issue. With 26 image it works well. After update to 29 image android tests fails. Emulator is connected ``` adb devices -l List of...

> Do you mind providing a sample project that reproduces the issue? I can't share this project, it's prohibited. But I can try to reproduce this issue at sample project

> > First launchable test method in first test class always takes too long time. It runs in ~20s. The next tests takes 0.5 - 2s. > > The same...

> > Is it possible to cache and share Layoutlib between all modules? > > This is a Gradle design issue. Each module has its own test task, which I...

I have tried an android screenshot testing (https://developer.android.com/studio/preview/compose-screenshot-testing). It works faster than paparazzi, but it should use the same mechanics, I think. 

I have created a new empty project with 2 screens and 6 paparazzi tests. The test takes 3s on initialization. Is it ok?  

> > First launchable test method in first test class always takes too long time. It runs in ~20s. The next tests takes 0.5 - 2s. > > The same...