
Jenkins needs some kind of report from the JUnit tests in order to tell whether the tests succeeded or not. android-junit-report is a library to do exactly that. With this setup, Jenkins should now successfully understand the status of the JUnit tests, where before it just ran them and ignored the results
22 lines
1.1 KiB
XML
22 lines
1.1 KiB
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!-- package name must be unique so suffix with "tests" so package loader doesn't ignore us -->
|
|
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
|
|
package="org.fdroid.fdroid.tests"
|
|
android:versionCode="1"
|
|
android:versionName="1.0">
|
|
<!-- We add an application tag here just so that we can indicate that
|
|
this package needs to link against the android.test library,
|
|
which is needed when building test cases. -->
|
|
<application>
|
|
<uses-library android:name="android.test.runner"/>
|
|
</application>
|
|
<!--
|
|
This declares that this application uses the instrumentation test runner targeting
|
|
the package of org.fdroid.fdroid. To run the tests use the command:
|
|
"adb shell am instrument -w org.fdroid.fdroid.tests/android.test.InstrumentationTestRunner"
|
|
-->
|
|
<instrumentation android:name="com.zutubi.android.junitreport.JUnitReportTestRunner"
|
|
android:targetPackage="org.fdroid.fdroid"
|
|
android:label="Tests for org.fdroid.fdroid" />
|
|
</manifest>
|