This removes ambiguity as to which modules are being imported, making
import slightly faster as Python doesn't need to test so many
directories for file presence.
All files should already be using absolute imports because mach command
modules aren't imported to the package they belong to: they instead
belong to the "mach" package. So relative imports shouldn't have been
used.
--HG--
extra : commitid : 6tFME1KKfTD
extra : rebase_source : 78728f82f5487281620e00c2a8004cd5e1968087
I want to include a file built during the Fennec build to the
roboextender extension; this is an easy way to arrange it.
I took the opportunity to make the extension file tree mirror the XPI
file tree, which always used base/.
--HG--
rename : testing/mochitest/roboextender/Makefile.in => mobile/android/tests/browser/robocop/roboextender/Makefile.in
rename : mobile/android/tests/browser/robocop/roboextender/SelectionUtils.js => mobile/android/tests/browser/robocop/roboextender/base/SelectionUtils.js
rename : mobile/android/tests/browser/robocop/roboextender/paymentsUI.html => mobile/android/tests/browser/robocop/roboextender/base/paymentsUI.html
rename : mobile/android/tests/browser/robocop/roboextender/robocop_home_banner.html => mobile/android/tests/browser/robocop/roboextender/base/robocop_home_banner.html
rename : mobile/android/tests/browser/robocop/roboextender/robocop_prompt_gridinput.html => mobile/android/tests/browser/robocop/roboextender/base/robocop_prompt_gridinput.html
rename : mobile/android/tests/browser/robocop/roboextender/testInputSelections.html => mobile/android/tests/browser/robocop/roboextender/base/testInputSelections.html
rename : mobile/android/tests/browser/robocop/roboextender/testSelectionHandler.html => mobile/android/tests/browser/robocop/roboextender/base/testSelectionHandler.html
rename : mobile/android/tests/browser/robocop/roboextender/testTextareaSelections.html => mobile/android/tests/browser/robocop/roboextender/base/testTextareaSelections.html
rename : testing/mochitest/roboextender/bootstrap.js => mobile/android/tests/browser/robocop/roboextender/bootstrap.js
rename : testing/mochitest/roboextender/chrome.manifest => mobile/android/tests/browser/robocop/roboextender/chrome.manifest
rename : testing/mochitest/roboextender/install.rdf => mobile/android/tests/browser/robocop/roboextender/install.rdf
rename : testing/mochitest/roboextender/moz.build => mobile/android/tests/browser/robocop/roboextender/moz.build
extra : commitid : 2BkQaW1ESSI
extra : rebase_source : cd7ca3327f77584542a77b26519c9a812f48c48e
extra : histedit_source : fe49f2ab0b6193b49a8c5c5cf4da51a5a4b993f7
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!
--HG--
extra : rebase_source : a5ab08222110a20291aebe70ef1fda0d340dbe7d
extra : source : e91ac9a35f86928fcd519911476ee7d68d06f921
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.
--HG--
extra : rebase_source : b84246ab327c7ec576d82cc4b516e729978600c7
extra : histedit_source : 9b23a6f66e6422e5f334f31cea2a21036be45543
