Mochitests on b2g desktop are no longer being run on any trunk branches, including
b2g-inbound. Dropping support for it significantly reduces complexity
in the mochitest harness.
Mochitests on b2g desktop are no longer being run on any trunk branches, including
b2g-inbound. Dropping support for it significantly reduces complexity
in the mochitest harness.
This adds a flag to |mach robocop| that does everything to run a
Robocop test except launch the actual test. Instead of launching the
test, it starts the mochi.test server and launches Fennec with a test
profile; then it sits and waits forever.
This allows regular Java IDEs (IntelliJ, but previously Eclipse) to
run Robocop tests like regular instrumentation tests, "injecting" them
into the prepared testing environment. It's quite nice!
This patch declares robocop.ini an instrumentation manifest. It's not
currently possible to declare tests that don't correspond to files, so
we include the .java extension. (This could be revisited.)
In |mach robocop|, we use the generic test resolving infrastructure to
select the 'instrumentation'/'robocop' flavor/subsuite tests. In
|runtestsremote.py|, we fall back to robocop.ini, as we always have.
This adds a flag to |mach robocop| that does everything to run a
Robocop test except launch the actual test. Instead of launching the
test, it starts the mochi.test server and launches Fennec with a test
profile; then it sits and waits forever.
This allows regular Java IDEs (IntelliJ, but previously Eclipse) to
run Robocop tests like regular instrumentation tests, "injecting" them
into the prepared testing environment. It's quite nice!
This change was generated using the `autopep8` module [1]. To replicate:
$ pip install --upgrade autopep8
$ cd gecko
$ autopep8 -i -a -a -r testing/mochitest --exclude 'testing/mochitest/pywebsocket/*'
[1] https://github.com/hhatto/autopep8
--HG--
extra : rebase_source : fb127187cd488b977981338373d66cc8c735214f
Before a Robocop test starts, |recordLogcat| clears the |adb logcat| on
device. If a Robocop test fails, we print the logcat immediately after
the test. The moved call avoids printing the logcat after all tests
have completed, which avoids printing a spurious second copy. We still
print the logcat after running a Mochitest.
This patch stops pushing the obsolete fennec_ids.txt file to the testing
device and deletes the stale robotium.config file after the profile it
references is deleted.
