Added a loop for repeating the requested test(s).
With --run-until-failure, loop until a test fails.
With --repeat=N, repeat N times. eg, --repeat=1 implies 2 runs total (same as mochitest).
(Incidentally moved code for --enable-webrender since it was not in the appropriate section.)
Differential Revision: https://phabricator.services.mozilla.com/D50299
--HG--
extra : moz-landing-system : lando
This also updates the two functions (BrowserTestUtils.firstBrowserLoaded,
browser_broadcastchannel.js#browserFrameLoaded) that rely on the previous
event to use the new one.
Differential Revision: https://phabricator.services.mozilla.com/D49002
--HG--
extra : moz-landing-system : lando
All but browser_bug744745.js seem to pass even without the fixes I
made, which seems odd.
browser_bug1058164.js is a little odd because it passes in {} instead
of a boolean for the useCapture argument. I think this ends up calling
addEventListener(..., {}, false), which should be the equivalent of
addEventListener(..., {}).
Differential Revision: https://phabricator.services.mozilla.com/D49453
--HG--
extra : moz-landing-system : lando
Most of these tests have been disabled for a long time; they run well
in the current test environment.
With the additional tests running, task times increase; I have added one
more test chunk for android mochitest-plain.
These tests were identified from a random sampling of mochitest manifests;
I intend to enable more mochitests in future patches.
Differential Revision: https://phabricator.services.mozilla.com/D48912
--HG--
extra : moz-landing-system : lando
This leaves the testharness files, because they are used in various mochitests.
Differential Revision: https://phabricator.services.mozilla.com/D49132
--HG--
extra : moz-landing-system : lando
This leaves the testharness files, because they are used in mochitest-chrome
tests in dom/animation/test.
Differential Revision: https://phabricator.services.mozilla.com/D49132
--HG--
extra : moz-landing-system : lando
This leaves the testharness files, because they are used in mochitest-chrome
tests in dom/animation/test.
Differential Revision: https://phabricator.services.mozilla.com/D49132
--HG--
extra : moz-landing-system : lando
Due to limitations in the test harness, the "serviceworker_e10s" (for mochitest
and xpcshell) and "sw-e10s" (for WPT) values will match mozinfo's "nightly_build"
value, unless overridden by "--setpref dom.serviceWorkers.parent_intercept=..."
provided at the CLI.
Differential Revision: https://phabricator.services.mozilla.com/D43170
--HG--
extra : moz-landing-system : lando
Due to limitations in the test harness, the "serviceworker_e10s" (for mochitest
and xpcshell) and "sw-e10s" (for WPT) values will match mozinfo's "nightly_build"
value, unless overridden by "--setpref dom.serviceWorkers.parent_intercept=..."
provided at the CLI.
Differential Revision: https://phabricator.services.mozilla.com/D43170
--HG--
extra : moz-landing-system : lando
mochitest-chrome is not supported with geckoview and attempts to run chrome
tests with geckoview result in a hang. mach test runs can accidentally attempt
to run chrome tests if the flavor is not specified and the directory contains
a chrome.ini manifest.
Existing harness support allows for filtering flavors based on buildapp, like
android, but not by run-time app like geckoview, so this patch disables
mochitest-chrome for all android runs.
Differential Revision: https://phabricator.services.mozilla.com/D47943
--HG--
extra : moz-landing-system : lando
Removes all the robocop test files and most robocop support. @RobocopTarget annotations and some build configuration is intentionally left untouched at this time, in case there is additional risk involved; a good task for follow-up.
Differential Revision: https://phabricator.services.mozilla.com/D45671
--HG--
extra : moz-landing-system : lando
Add new preference `extensions.webextensions.warnings-as-errors` that
defaults to `true` in tests. Tests that expect warnings are modified
to briefly flip the pref for the specific part of the test that needs
an exception.
As part of the refactor, log entries for schema entries that contain
`"onError": "warn"` will now be prefixed by "Warning" instead of
"Error", to be consistent with the change from bug 1495908.
Differential Revision: https://phabricator.services.mozilla.com/D40548
--HG--
extra : moz-landing-system : lando
Add new preference `extensions.webextensions.warnings-as-errors` that
defaults to `true` in tests. Tests that expect warnings are modified
to briefly flip the pref for the specific part of the test that needs
an exception.
As part of the refactor, log entries forschema entries that contain
`"onError": "warn"` will now be prefixed by "Warning" instead of
"Error", to be consistent with the change from bug 1495908.
Differential Revision: https://phabricator.services.mozilla.com/D40548
--HG--
extra : moz-landing-system : lando
Remove test manifest annotations that specifically target fennec,
or likely target the android 4.3 emulator.
Differential Revision: https://phabricator.services.mozilla.com/D45018
--HG--
extra : moz-landing-system : lando
If there are no stored logins, the Cancel button is hidden.
If there are visible stored logins, clicking the Cancel button will exit and move to the first login in the list.
If there are no visible stored logins, clicking the Cancel button will reset the search filter, exit, and move to the first login in the list.
This patch also fixes a race condition where we could end up with multiple observer notifications if about:logins was loaded multiple times very quickly.
Differential Revision: https://phabricator.services.mozilla.com/D43544
--HG--
extra : moz-landing-system : lando
This patch adds a test case to check the visibility of the track counter
is correct in different situations, including zero tracker, one tracker
and multiple trackers.
Also, this patch fixes an issue that the
BrowserTestUtils.waitForAttributes() won't work if the waiting
attributes doesn't have a value or has an empty string as its value.
We check the value of the observing attribute to verify if it is
existing, however an empty string will be treated as a false, so it
won't pass the check if the attribute doesn't have a value. Hence, we
should use hasAttribute() instead of getAttribute() to check the
existence of the attribute.
Differential Revision: https://phabricator.services.mozilla.com/D42718
--HG--
extra : moz-landing-system : lando
This picks up various improvements, especially to how configurations are handled and some new rules.
Differential Revision: https://phabricator.services.mozilla.com/D37271
--HG--
extra : moz-landing-system : lando
Prior to this patch, assertions in SpecialPowers.spawn callbacks only work
when the caller was in a window with a SimpleTest harness.
This patch fixes that by registering a default assertion handler at the start
of a test, and sending assertions from any task without its own harness to
said default handler.
MANUAL PUSH: Contains complex rename operations that I don't trust Lando to
handle correctly.
Differential Revision: https://phabricator.services.mozilla.com/D42210
--HG--
extra : rebase_source : b0b72ce166647621a50aad0af8f130c0d89e3829
extra : source : 41b6d03a870caa7c4be2146ce8c8d84efdb20e79
Gurzau Raul
Geoff Brown
Kashav Madan
Geoff Lankow
Andrew McCreight
Christian Holler
Brian Grinstead
Ms2ger
shindli
Andrew Halberstadt
Kris Maglione
Johann Hofmann
Perry Jiang
Neil Deakin
Daniel Varga
Nika Layzell
Christoph Kerschbaumer
Matthew Noorenberghe
Rob Wu
Narcis Beleuzu
Gijs Kruitbosch
Edwin Takahashi
Jared Wein
Sylvestre Ledru
Tim Huang
Mark Banner
mcrawford
Abdoulaye O. Ly
Oana Pop Rus