summaryrefslogtreecommitdiff
path: root/test/cli.t
diff options
context:
space:
mode:
Diffstat (limited to 'test/cli.t')
-rw-r--r--test/cli.t13
1 files changed, 9 insertions, 4 deletions
diff --git a/test/cli.t b/test/cli.t
index 9771c56..b19e8d4 100644
--- a/test/cli.t
+++ b/test/cli.t
@@ -247,11 +247,16 @@ not embedded in the help text above: this pin would then have to be edited
every release, for no gain. The Makefile's release target asserts the built
binary reports the version it just wrote, so the two cannot drift.
- $ colitur --version
- 0.1.0
+The SHAPE is pinned here, not the value. Pinning the literal would mean
+editing this test on every release for no gain, and the value is already
+asserted where it can actually drift: the Makefile's release target requires
+the freshly built binary to report the version it just wrote.
- $ colitur -V
- 0.1.0
+ $ colitur --version | grep -cE '^[0-9]+\.[0-9]+\.[0-9]+$'
+ 1
+
+ $ test "$(colitur --version)" = "$(colitur -V)" && echo same
+ same
Agreement with the package metadata (dune-project's own (version ...), which
generates colitur.opam) is NOT asserted here: the cram sandbox has no source