While it might seem like a good idea to disable all of the checks we don't
currently pass, Intellij uses the same lint configuration file as the
command-line invocation and so we'll be more likely to write in new errors by
disabling some checks.
--HG--
extra : commitid : 23gdgWSBmyt
extra : source : 7bd754d48b86b5104bc44067886af81c9315a3b6
This doesn't work for the Settings screen (bug 1170346).
--HG--
extra : commitid : 4Nfxo9FZGRp
extra : rebase_source : 0246d346d8ba5c21624d9bbfa26f14d6c30d37fd
These patches added complexity that we're removing by implementing this bug.
--HG--
extra : commitid : LqUrYf52Qbo
extra : rebase_source : 3ef8e5fc5059c6aa6d28d2fc5a2cca2381904986
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
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 : 15e9e8d5c311312e2eb317936e5d154237c1f9a3
extra : histedit_source : 050ac958ae8580f45e5011a0d353bf13e65d5ff3
DONTBUILD NPOTB
Unfortunately, Gradle just can't handle incremental dexing in our
multi-project and parallel configuration. I see the dreaded
"com.android.dex.DexException: Multiple dex files define ..." error
frequently.
I'm using a downloaded Robotium package instead of the in-tree JAR
file as well, 'cuz it seems to be related.
--HG--
extra : rebase_source : d95c0844082a6deb48966496cb90824f70f6c49d
extra : histedit_source : 2f3d231d9b7139880a924089ab0d523e5e31e6b6
Ryan VanderMeulen
Michael Comella
"Chris AtLee"
Nick Alexander
James Willcox
Allison Naaktgeboren
Chenxia Liu
Eitan Isaacson
Liang-Heng Chen
Carsten "Tomcat" Book
Phil Ringnalda
Ted Mielczarek
Richard Newman
Randall Barker
Andrew Osmond
Dipti Nirmale
Martyn Haigh