Android Unit Tests running for hours

[MichBogus]

Hello!

On our project we do have two different packages in androidTest. One is for Espresso tests only, and second one is for Android unit testing. Right now we do have two separate tasks for building each package, but after going for gradle 3.x from 2.x we are occurring problem with tests from Android unit tests package. For some odd reason they are building like Espresso tests and instead of going for max 3 minutes, they take hours to run (there are over 1400 of them so you can get the idea how it feels).

Of course we are using typical spoon configuration

spoon { debug = true if (project.hasProperty('espresso')) { instrumentationArgs = ["package=espresso"] } else if (project.hasProperty('unit')) { instrumentationArgs = ["package=pl.araneo.farmadroid"] //going for 1,5h instead of 3 minutes } sequential = false grantAllPermissions = true noAnimations = true }

And tasks for it:

task androidUnitTestIZI(dependsOn: 'spoonDebugAndroidTest') task instrumentationTestIZI(dependsOn: 'spoonDebugAndroidTest')

Do you have any idea?
P.S. on old Spoon everything was going really nice.

Thanks

[jaredsburrows]

Are you still seeing this?