summaryrefslogtreecommitdiff
path: root/package.json
diff options
context:
space:
mode:
authorojacobson <ojacobson@noreply.codeberg.org>2025-05-30 21:13:28 +0200
committerojacobson <ojacobson@noreply.codeberg.org>2025-05-30 21:13:28 +0200
commit414de683b23d0c14a56934bc04f930301b369035 (patch)
tree00c860d1f0fea005583c67330ae63dd6594f92da /package.json
parent7a5c82d9b86e0a0828f4ccaac42b2db398945406 (diff)
parent515cd2dbe6f202c92b938c4f7364c97b4eac9ab1 (diff)
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.
Diffstat (limited to 'package.json')
-rw-r--r--package.json4
1 files changed, 1 insertions, 3 deletions
diff --git a/package.json b/package.json
index 85099e8..4501576 100644
--- a/package.json
+++ b/package.json
@@ -8,9 +8,7 @@
},
"scripts": {
"lint": "prettier --check ui && eslint ui",
- "format": "prettier --write ui",
- "test": "vitest",
- "coverage": "vitest run --coverage"
+ "format": "prettier --write ui"
},
"devDependencies": {
"@sveltejs/adapter-static": "^3.0.8",