|
@@ -22,9 +22,9 @@ and executes Spoon with a few arguments:
|
22
|
22
|
|
23
|
23
|
{{< highlight bash >}}
|
24
|
24
|
java -jar spoon-runner.jar \
|
25
|
|
- --apk application.apk
|
26
|
|
- --test-apk applicationTests.apk
|
27
|
|
- --fail-on-failure
|
|
25
|
+ --apk application.apk \
|
|
26
|
+ --test-apk applicationTests.apk \
|
|
27
|
+ --fail-on-failure \
|
28
|
28
|
--fail-if-no-device-connected
|
29
|
29
|
{{< / highlight >}}
|
30
|
30
|
|
|
@@ -34,6 +34,8 @@ the form factors and API versions that are important to us; if any test fails
|
34
|
34
|
on any of those devices, Spoon will return an error code and the build will
|
35
|
35
|
fail.
|
36
|
36
|
|
|
37
|
+<!--more-->
|
|
38
|
+
|
37
|
39
|
For library projects, you only have a single APK containing both the tests
|
38
|
40
|
and the library itself. The current version of Spoon requires both `--apk` and
|
39
|
41
|
`--test-apk` to be specified, so we simply pass in the same APK to both. It
|