Bug 1734084 - [remote] Fix indentation of commands in remote/doc/Testing.md r=webdriver-reviewers,whimboo
authorJulian Descottes <jdescottes@mozilla.com>
Tue, 05 Oct 2021 08:06:54 +0000
changeset 594548 55b7ab90b26c02ca9f84de3ba43bef5f98bf3936
parent 594547 54e78f8e35de07fdbdf0527e3eaf68e4f48ade3b
child 594549 ebd8d0a44d346bbeed3bcd2058b7703b9124beb3
push id38849
push usernerli@mozilla.com
push dateTue, 05 Oct 2021 15:48:45 +0000
treeherdermozilla-central@04a3446f3ae3 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewerswebdriver-reviewers, whimboo
bugs1734084
milestone95.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 1734084 - [remote] Fix indentation of commands in remote/doc/Testing.md r=webdriver-reviewers,whimboo This is only a whitespace change, but it prevented the commands from being correctly rendered in our documenation. Differential Revision: https://phabricator.services.mozilla.com/D127518
remote/doc/Testing.md
--- a/remote/doc/Testing.md
+++ b/remote/doc/Testing.md
@@ -120,17 +120,17 @@ how to skip tests, run only one test or 
 
 Puppeteer tests are vendored under _remote/test/puppeteer/_ and are
 run locally like this:
 
 	% ./mach puppeteer-test
 
 You can also run them against Chrome as:
 
-  % ./mach puppeteer-test --product=chrome --subset
+	% ./mach puppeteer-test --product=chrome --subset
 
 `--subset` disables a check for missing or skipped tests in our log parsing.
 This check is typically not relevant when running against Chrome.
 
 Test expectation metadata is collected in _remote/test/puppeteer-expected.json_
 via log parsing and a custom Mocha reporter under
 _remote/test/puppeteer/json-mocha-reporter.js_
 
@@ -140,15 +140,15 @@ Testing on Try
 
 To schedule all the Remote Protocol tests on try, you can use the
 `remote-protocol` [try preset]:
 
 	mach try --preset remote-protocol
 
 But you can also schedule tests by selecting relevant jobs yourself:
 
-  mach try fuzzy
+	mach try fuzzy
 
 [Puppeteer test suite]: https://github.com/puppeteer/puppeteer/blob/master/test/README.md
 [track progress]: https://puppeteer.github.io/ispuppeteerfirefoxready/
 [Puppeteer support]: https://bugzilla.mozilla.org/show_bug.cgi?id=puppeteer
 [Mocha]: https://mochajs.org/
 [try preset]: https://firefox-source-docs.mozilla.org/tools/try/presets.html