76
edits
Auto-tools/Projects/Robocop: Difference between revisions
→Problem
(→Setup) |
|||
| Line 1: | Line 1: | ||
= Problem = | == Problem == | ||
With advent of NativeFennec, a new framework was needed to test the UI of the Mobile Browser. Robotium was identified as a useful framework to take advantage of, but is not complete. Robocop incorporates all of Activity, Instrumentation, and Robotium Classes to inject events into the new Java front-end of Fennec. | With advent of NativeFennec, a new framework was needed to test the UI of the Mobile Browser. Robotium was identified as a useful framework to take advantage of, but is not complete. Robocop incorporates all of Activity, Instrumentation, and Robotium Classes to inject events into the new Java front-end of Fennec. | ||
| Line 37: | Line 37: | ||
From the Fennec's objdir (using testLoad as an example): | From the Fennec's objdir (using testLoad as an example): | ||
<pre>TEST_PATH=testLoad make mochitest-robotium</pre> | <pre>TEST_PATH=testLoad make mochitest-robotium</pre> | ||
== Updating your test directory == | |||
It is not always necessary to rebuild Fennec to use new tests. If you are updating the build with your own test, ensure that your test has been added to the manifest in /PATH/TO/FENNEC/SOURCE/mobile/android/base/tests/robocop.ini . | |||
Otherwise, you can retrieve tests from the repository by executing: | |||
<pre> | |||
hg pull | |||
hg update</pre> | |||
Now you can build the robocop part of Fennec by executing: | |||
<pre> | |||
cd objdir | |||
make -C build/mobile/robocop/ | |||
make package </pre> | |||
== Frequently found Errors == | == Frequently found Errors == | ||