aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorYuchen Pei <hi@ypei.me>2021-12-08 21:33:06 +1100
committerYuchen Pei <hi@ypei.me>2021-12-08 21:33:06 +1100
commit1cd0bf69a60d9cc1025d5ea760139e14ded526a9 (patch)
treef090b1b123aff9442d195e64ce30b9ba3789c3f8 /README
parent363292644c504033b35b1dfff1342c35f17d66f4 (diff)
Minor formatting fix
Diffstat (limited to 'README')
-rw-r--r--README14
1 files changed, 6 insertions, 8 deletions
diff --git a/README b/README
index 14a2d83..2a3c065 100644
--- a/README
+++ b/README
@@ -43,38 +43,36 @@ HEADLESS TESTS:
To launch the test suite from the command line, ensure the extension
has been built with automated test suite. Then install
selenium-webdriver and geckodriver, and ensure the latter is in $PATH:
-
$ npm install selenium-webdriver
$ npm install geckodriver
$ export PATH=$PATH:./node_modules/.bin
Now you can invoke the test with
-
$ node ./test.js
which will print out a summary of test results.
Optionally you can also test with a chosen seed
-
$ node ./test.js 12345
HEADLESS COMPLIANCE CHECK:
-To check whether a webpage is LibreJS-compliant from the command line, ensure that the extension has NOT been built with automated test suite. Then install selenium-webdriver and geckodriver, and ensure the latter is in $PATH:
-
+To check whether a webpage is LibreJS-compliant from the command line,
+ensure that the extension has NOT been built with automated test
+suite. Then install selenium-webdriver and geckodriver, and ensure the
+latter is in $PATH:
$ npm install selenium-webdriver
$ npm install geckodriver
$ export PATH=$PATH:./node_modules/.bin
Now you can check a webpage for compliance with
-
$ node ./compliance.js <url>
-It will open the url in a headless browser, save a screenshot, and output the compliance check result.
+It will open the url in a headless browser, save a screenshot, and
+output the compliance check result.
For example, to check the compliance of the FSF homepage, do
-
$ node ./compliance.js https://fsf.org