I set my project up to run with Robolectric and the the gradle-android-test-plugin. This all works fine and first tests are running and failing.
If a test fails this will also fail the gradle build. Is there a way to just let the build go on and write down the failing tests for evaluation in a later step?
The plan is to integrate the testing in a continuous integration server and there the build should only be unstable if a test fails.
Hmm. Well you have two options I think. One is to use
to not let the task fail when a test fails.
Another approach would be to run your gradle command with '--continue'. This will execute as many tasks as possible and list the failed tasks at the end and not stop after the first task has failed.
The correct syntax with AndroidConnectedTests is as following:
Now the test task is not failing the build anymore and you can pick up the failed tests with your build server to markt the build as unstable etc.