aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorYuchen Pei <hi@ypei.me>2022-07-28 15:32:10 +1000
committerYuchen Pei <hi@ypei.me>2022-07-28 15:32:10 +1000
commit5b10a10743b8459f64fe83e0ff420f69da79c9a4 (patch)
treec61904d688247790181d4955a4074b8c94302c03 /docs
parentb98cb70b1bcd5b211aaa5d2675f96416911c0647 (diff)
Moving scripts and utilities into a new utilities dir
Diffstat (limited to 'docs')
-rw-r--r--docs/librejs.texi10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/librejs.texi b/docs/librejs.texi
index c9c562c..243425a 100644
--- a/docs/librejs.texi
+++ b/docs/librejs.texi
@@ -677,14 +677,14 @@ selenium-webdriver and geckodriver, and ensure the latter is in $PATH:
Now you can invoke the test with
@verbatim
- $ node ./test.js
+ $ node ./utilities/test.js
@end verbatim
which will print out a summary of test results.
Optionally you can also test with a chosen seed
@verbatim
- $ node ./test.js 12345
+ $ node ./utilities/test.js 12345
@end verbatim
@section Headless compliance check
@@ -700,7 +700,7 @@ latter is in $PATH:
Now you can check a webpage for compliance with
@verbatim
- $ node ./compliance.js <url>
+ $ node ./utilities/compliance.js <url>
@end verbatim
It will open the url in a headless browser, save a screenshot, and
@@ -708,12 +708,12 @@ output the compliance check result.
For example, to check the compliance of the FSF homepage, do
@verbatim
- $ node ./compliance.js https://fsf.org
+ $ node ./utilities/compliance.js https://fsf.org
@end verbatim
@section Adding new whitelisted libraries
-The script index.js in @file{./hash_script} generates the default
+The script index.js in @file{./utilities/hash_script} generates the default
whitelist. Run it with the following command:
@command{node index.js > output}