Files
Lauri Ojansivu 1218cd281f Add test-menu.sh and checked-in example inputs for docs/Features
test-menu.sh mirrors the docs/Features menu structure and runs the actual
WeKan code for each feature: a dedicated runner for Login (a real REST
username/password round trip) and ImportExport/PDF (create a board, export
it, check the PDF header), and a generic fallback that matches a feature
against this repo's own automated tests by filename. Every feature run
writes output.txt/result.txt/run.log under .tools/test-menu/<timestamp>/,
mirroring the docs/Features path, and never leaves an empty or missing
result.

The example INPUT for a feature is checked into the repository next to its
documentation instead: docs/Features/<path>/example-input.txt, hand-written
for Login and ImportExport/PDF and extracted from the feature's own .md
elsewhere. test-menu.sh only reads these; it never writes into docs/Features.

An earlier version of the matcher also grep'd test file CONTENTS for a
keyword once the filename search failed, which pulled in noise (a word like
"webhook" mentioned in passing in a dozen unrelated tests); it is
filename-only now.

Thanks to xet7.
2026-09-08 17:49:24 +03:00

7 lines
312 B
Plaintext

# Example input for docs/Features/Admin-Panel/Problems, from Design.md.
# Extracted automatically from the first fenced code block in that
# document - see Design.md for the full explanation.
{ stream, bleed, category, action, source, severity, cwe,
count: 1043, firstAt: <first seen>, at: <last seen>, … }