summaryrefslogtreecommitdiff
path: root/test
diff options
context:
space:
mode:
Diffstat (limited to 'test')
-rw-r--r--test/cli.t18
1 files changed, 18 insertions, 0 deletions
diff --git a/test/cli.t b/test/cli.t
index d7e86f7..419e7f0 100644
--- a/test/cli.t
+++ b/test/cli.t
@@ -241,3 +241,21 @@ Every command the help lists is a command the binary actually accepts. This
is the check that catches help text drifting away from the dispatch:
$ for c in easter temporal day readings; do colitur $c 2026 > /dev/null || echo "$c FAILED"; done
+
+--version prints the version alone, to standard output, exit 0. Deliberately
+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
+
+ $ colitur -V
+ 0.1.0
+
+Agreement with the package metadata (dune-project's own (version ...), which
+generates colitur.opam) is NOT asserted here: the cram sandbox has no source
+tree to read dune-project from. It is asserted in the Makefile's release
+target instead, which rewrites both and then requires the freshly built
+binary to report the version it just wrote -- the point in time where a drift
+between the two could actually be introduced.