Wed, 31 Dec 2014 07:22:50 +0100
Correct previous dual key logic pending first delivery installment.
1 Robocop Mochitest
2 =================
4 *Robocop Mochitest* tests run on Native Android builds marked with an
5 'rc' in TBPL. These are Java based tests which run from the mochitest
6 harness and generate similar log files. These are designed for
7 testing the native UI of Android devices by sending events to the
8 front end.
10 See the documentation at
11 https://wiki.mozilla.org/Auto-tools/Projects/Robocop/WritingTests for
12 details.
14 Development cycle
15 -----------------
17 To deploy the robocop APK to your device and start the robocop test
18 suite, use::
20 make -C $OBJDIR mochitest-robocop
22 To run a specific test case, such as ``testLoad``::
24 make -C $OBJDIR mochitest-robocop TEST_PATH=testLoad
26 The Java files in ``mobile/android/base/tests`` are dependencies of the
27 robocop APK built by ``build/mobile/robocop``. If you modify Java files
28 in ``mobile/android/base/tests``, you need to rebuild the robocop APK
29 with::
31 mach build build/mobile/robocop
33 Changes to ``.html``, ``.css``, ``.sjs``, and ``.js`` files in
34 ``mobile/android/base/tests`` do not require rebuilding the robocop
35 APK -- these changes are always 'live', since they are served by the
36 mochitest HTTP server and downloaded each test run by your device.
38 ``mach package`` does build and sign a robocop APK, but ``make
39 mochitest-robocop`` does not use it. (This signed APK is used to test
40 signed releases on the buildbots).
42 As always, changes to ``mobile/android/base``, ``mobile/android/chrome``,
43 ``mobile/android/modules``, etc., require::
45 mach build mobile/android/base && mach package && mach install
47 as usual.