summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorbill-auger <mr.j.spam.me@gmail.com>2024-03-27 19:52:29 -0400
committerbill-auger <mr.j.spam.me@gmail.com>2024-03-28 23:15:25 -0400
commitf64d9ed3aab49373845147c1e8044df366a75393 (patch)
treeb24ae813ba4b3fb7959190e27e57ec87a3237a79
parentc9cc64d5096f2813e3ea026542093e0007600ffc (diff)
update docs
-rw-r--r--HACKING/HACKING_testing.md25
1 files changed, 11 insertions, 14 deletions
diff --git a/HACKING/HACKING_testing.md b/HACKING/HACKING_testing.md
index 8dee485..07f04ef 100644
--- a/HACKING/HACKING_testing.md
+++ b/HACKING/HACKING_testing.md
@@ -1,18 +1,15 @@
Testing
=======
-Please write unit tests for new things. Tests can be run with `make
-check`, which just runs `./testenv roundup` in the `test/` directory.
-Relatedly, you need the `roundup` (the `sh-roundup` package on
-Parabola) tool to run the tests. `./testenv` can be given
-`--no-network` and/or `--no-sudo` to dissable tests that require those
-things. Make can be made to pass those things in by setting
-`TESTENVFLAGS`. If you don't dissable either, I *strongly* recommend
-setting TMPDIR to somewhere on a btrfs partition before running the
-tests; otherwise the chroot tests will take forever. I mean, they
-already take long on btrfs, but without it... _dang_.
+Please write unit tests for new things. Tests can be run with `make check`,
+which just runs `./testenv bats cases` in the `test/` directory. You will need
+the `bats` tool (the `bash-bats` Parabola package) in order to run the tests.
+`./testenv` can be given `--no-network` and/or `--no-sudo` to dissable tests
+which require those things. You can also pass them to make as `TESTENVFLAGS`.
+If you don't dissable either, I *strongly* recommend setting TMPDIR to somewhere
+on a btrfs partition before running the tests; otherwise the chroot tests will
+take forever. I mean, they already take long on btrfs, but without it... _dang_.
-I also recommend having the `haveged` daemon running. That's good
-general advice, but also: some of the tests make GPG keys, this
-"should" take on the order of 1 second, but can take several minutes
-if you don't have `haveged` running.
+I also recommend having the `haveged` daemon running. Some of the tests generate
+GPG keys. This "should" take on the order of 1 second, but can take several
+minutes if you don't have `haveged` running.