diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-20 12:02:47 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-20 12:02:47 -0500 |
| commit | 01c6c5331defc24f94bf1f667b7f57e0072733b9 (patch) | |
| tree | 295e261faf6b14a548d94f63d61c1eb459b0cd1b /scripts | |
| parent | 4e2d8006215da6f5b08c1de360d7cb842ca8de95 (diff) | |
| download | archsetup-01c6c5331defc24f94bf1f667b7f57e0072733b9.tar.gz archsetup-01c6c5331defc24f94bf1f667b7f57e0072733b9.zip | |
docs: document the unit-test layer and add a make test-unit target
The README only covered the VM integration harness. The unit suites under tests/ (one directory per script, fake binaries on PATH) went unmentioned, so a contributor adding a .local/bin script had no way to know they existed or how to run them.
I added a make test-unit target that runs every tests/*/test_*.py suite explicitly. unittest discover can't find them because the per-script directory names are hyphenated and aren't valid package paths. Then I split the README Testing section into Unit and VM-integration layers, added a guide for adding a suite, and pointed Contributing at test-unit for script changes.
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions