README.md revision 76e306183bb8c3935c091a558690edc310edbd70
ef28ad515cc0858ccbfba09e17a844052ed79356Tom Rumsey#Running tests
ef28ad515cc0858ccbfba09e17a844052ed79356Tom RumseyIn order to run the tests, run the following command:
ef28ad515cc0858ccbfba09e17a844052ed79356Tom Rumsey./gradlew generateCoverage
ef28ad515cc0858ccbfba09e17a844052ed79356Tom RumseyThis will both run the unit tests, and generate a coverage report.
ef28ad515cc0858ccbfba09e17a844052ed79356Tom RumseyThe unit test report is located at:
ef28ad515cc0858ccbfba09e17a844052ed79356Tom Rumsey{baseFolder}/app/build/reports/tests/debug/index.html
ef28ad515cc0858ccbfba09e17a844052ed79356Tom RumseyThe coverage report is located at:
ef28ad515cc0858ccbfba09e17a844052ed79356Tom Rumsey{baseFolder}/app/build/reports/jacoco/generateCoverage/html/index.html
ef28ad515cc0858ccbfba09e17a844052ed79356Tom RumseyNote that the coverage report will not be generated if there are any test failures.
ef28ad515cc0858ccbfba09e17a844052ed79356Tom RumseyThe target is to have a large coverage for non android classes (e.g. non ui and database classes)
76e306183bb8c3935c091a558690edc310edbd70Tom Rumsey# Instrumentation tests
76e306183bb8c3935c091a558690edc310edbd70Tom RumseyTo run the instrumentation tests, first connect and unlock the test devices, or start emulators.
76e306183bb8c3935c091a558690edc310edbd70Tom RumseyThen, run: ./gradlew spoon
76e306183bb8c3935c091a558690edc310edbd70Tom RumseyThe report for this should appear in :