AndroidGradleTests

Variations of gradle builds that setup unit and/or instrumentation tests

This repository showcases some setups of how different frameworks can be implemented in a gradle build configuration to test android applications.

Testing frameworks

###Robolectric

• Testing: TDD, JUnit4
• Advantages:
  • Tests can use JUnit4 instead of JUnit3
  • Tests are executed on local machine
  • Runs without Emulator or RealDevice
• Used in RobolectricEspresso

###RoboSpock

• glues Robolectric and Spock together
• Testing: TDD
• Advantages:
  • As tests are run with Robolectric it runs equally fast
  • Failing tests provide better information due to Spock
• Disadvatages:
  • Needs a second test project to run RoboSpock tests
• Used in RoboSpockEspresso

###Espresso

• Testing: Integration
• Advantages:
  • Good readability of produced tests
• Disadvatages:
  • currently not in a central repository -> has to be included manualy in libs
• Used in RobolectricEspresso RoboSpockEspresso