Consolidate testing steps into `tools/test`.

I've opted to run with `--coverage` to ensure that we continue exercising coverage support. Hat tip to @wlonk for holding me accountable on this - I had thought coverage was broken, but I was holding it wrong.

Also adjusts the code coverage failure thresholds to match here-and-now reality. I'm not offering a policy thought here, just making sure we

1. use the coverage checking we have, and
2. set standards we are actually achieving.

This was originally part of [another proposal][pr-6]. I've broken it out to make the intent clearer, and to make the proposal easier to get a handle on in isolation from other, related changes. Thanks to @wlonk for their input on this!

[pr-6]: https://codeberg.org/ojacobson/pilcrow/pulls/6

Merges prop/test-tool into main.

1 files changed, 13 insertions, 0 deletions

diff --git a/tools/test b/tools/test
new file mode 100755
index 0000000..06e2159
--- /dev/null
+++ b/tools/test
@@ -0,0 +1,13 @@
+#!/bin/bash -e
+
+## tools/test
+##
+## Run the full test suite.
+##
+## Best run as `tools/test` even if you have the `tools` directory in your
+## $PATH, due to naming collisions with the `test` shell builtin or `/bin/test`.
+
+cd "$(dirname "$0")/.."
+
+npx vitest --run --coverage
+cargo test