1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/mobile/android/base/tests/README.rst Wed Dec 31 06:09:35 2014 +0100
1.3 @@ -0,0 +1,47 @@
1.4 +Robocop Mochitest
1.5 +=================
1.6 +
1.7 +*Robocop Mochitest* tests run on Native Android builds marked with an
1.8 +'rc' in TBPL. These are Java based tests which run from the mochitest
1.9 +harness and generate similar log files. These are designed for
1.10 +testing the native UI of Android devices by sending events to the
1.11 +front end.
1.12 +
1.13 +See the documentation at
1.14 +https://wiki.mozilla.org/Auto-tools/Projects/Robocop/WritingTests for
1.15 +details.
1.16 +
1.17 +Development cycle
1.18 +-----------------
1.19 +
1.20 +To deploy the robocop APK to your device and start the robocop test
1.21 +suite, use::
1.22 +
1.23 + make -C $OBJDIR mochitest-robocop
1.24 +
1.25 +To run a specific test case, such as ``testLoad``::
1.26 +
1.27 + make -C $OBJDIR mochitest-robocop TEST_PATH=testLoad
1.28 +
1.29 +The Java files in ``mobile/android/base/tests`` are dependencies of the
1.30 +robocop APK built by ``build/mobile/robocop``. If you modify Java files
1.31 +in ``mobile/android/base/tests``, you need to rebuild the robocop APK
1.32 +with::
1.33 +
1.34 + mach build build/mobile/robocop
1.35 +
1.36 +Changes to ``.html``, ``.css``, ``.sjs``, and ``.js`` files in
1.37 +``mobile/android/base/tests`` do not require rebuilding the robocop
1.38 +APK -- these changes are always 'live', since they are served by the
1.39 +mochitest HTTP server and downloaded each test run by your device.
1.40 +
1.41 +``mach package`` does build and sign a robocop APK, but ``make
1.42 +mochitest-robocop`` does not use it. (This signed APK is used to test
1.43 +signed releases on the buildbots).
1.44 +
1.45 +As always, changes to ``mobile/android/base``, ``mobile/android/chrome``,
1.46 +``mobile/android/modules``, etc., require::
1.47 +
1.48 + mach build mobile/android/base && mach package && mach install
1.49 +
1.50 +as usual.
