bug 1497961: geckodriver: remove reference to MOZ_HEADLESS; r=me
authorAndreas Tolfsen <ato@sny.no>
Wed, 10 Oct 2018 19:00:54 +0100
changeset 499017 f19a279fec4cc06bc756178c6e3c92ffa0139512
parent 499016 454dfd00dd310576bd2c652ab302b7a6d53fe5fd
child 499018 5336690f90da7a1b9f08f13930996b205ecb62d1
push id1864
push userffxbld-merge
push dateMon, 03 Dec 2018 15:51:40 +0000
treeherdermozilla-release@f040763d99ad [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersme
bugs1497961
milestone64.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
bug 1497961: geckodriver: remove reference to MOZ_HEADLESS; r=me
testing/geckodriver/doc/Testing.md
--- a/testing/geckodriver/doc/Testing.md
+++ b/testing/geckodriver/doc/Testing.md
@@ -23,22 +23,23 @@ make sure you have built Firefox:
 
 	% ./mach build
 	% ./mach wpt testing/web-platform/tests/webdriver
 
 As these are functional integration tests and pop up Firefox windows
 sporadically, a helpful tip is to surpress the window whilst you
 are running them by using Firefox’ [headless mode]:
 
-	% MOZ_HEADLESS=1 ./mach wpt testing/web-platform/tests/webdriver
+	% ./mach wpt --headless testing/web-platform/tests/webdriver
 
-In addition to the `MOZ_HEADLESS` output variable there is also
-`MOZ_HEADLESS_WIDTH` and `MOZ_HEADLESS_HEIGHT` to control the
+The `--headless` flag is equivalent to setting the `MOZ_HEADLESS`
+output variable.  In addition to `MOZ_HEADLESS` there is also
+`MOZ_HEADLESS_WIDTH` and `MOZ_HEADLESS_HEIGHT` for controlling the
 dimensions of the no-op virtual display.  This is similar to using
-xvfb(1) which you may know from the X windowing system, but has
+Xvfb(1) which you may know from the X windowing system, but has
 the additional benefit of also working on macOS and Windows.
 
 As you get in to development of geckodriver and Marionette you will
 increasingly grow to understand our love for [trace-level logs].
 They provide us with the input—the HTTP requests—from the client
 (in WPT’s case from the tests’ use of a custom WebDriver client),
 the translation geckodriver makes to the [Marionette protocol],
 the log output from Marionette, its responses back to geckodriver,