summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorTor Andersson <tor@ccxvii.net>2025-04-29 12:22:38 +0200
committerTor Andersson <tor@ccxvii.net>2025-05-06 20:00:03 +0200
commitfcf6e38f68c22c1f1bbdb5f0f900d46d202d85a1 (patch)
tree67c4980c5f29fe582f7e9a52833358751652eba8 /docs
parent64f345c56447fb01e73c99827c028f6507a1514b (diff)
downloadserver-fcf6e38f68c22c1f1bbdb5f0f900d46d202d85a1.tar.gz
Add jsfuzz to npm dev-dependencies.
Diffstat (limited to 'docs')
-rw-r--r--docs/module/fuzzer.md19
1 files changed, 15 insertions, 4 deletions
diff --git a/docs/module/fuzzer.md b/docs/module/fuzzer.md
index d576693..3b05e70 100644
--- a/docs/module/fuzzer.md
+++ b/docs/module/fuzzer.md
@@ -17,17 +17,28 @@ Crash dumps are written to the "fuzzer" directory.
There are two fuzzers available:
-A fuzzer that uses the "jsfuzz" package.
+A simple fuzzer that plays completely randomly:
+
+ rtt fuzz-rand TITLE
+
+A more advanced fuzzer that uses the "jsfuzz" package.
With this fuzzer every title gets its own "fuzzer/corpus-title" sub-directory.
The corpus helps the fuzzer find interesting game states in future runs.
rtt fuzz TITLE
-A simple fuzzer that plays completely randomly:
+The fuzzer will run until you stop it or it has found too many errors.
- rtt fuzz-rand TITLE
+## Coverage
-The fuzzer will run until you stop it or it has found too many errors.
+Jsfuzz will generate a "nyc" coverage report that you can look at,
+to see how much of your code has been tested:
+
+ npx nyc coverage
+
+Or to generate an HTML report in "coverage":
+
+ npx nyc report --reporter=html
## Debug