diff options
| author | Ralph Amissah <ralph.amissah@gmail.com> | 2026-09-21 14:21:23 -0400 |
|---|---|---|
| committer | Ralph Amissah <ralph.amissah@gmail.com> | 2026-09-22 17:07:29 -0400 |
| commit | 4449ac39de863dc65521aea48b123adba7785fa4 (patch) | |
| tree | 006946f32a419e16153183fb2499096229e7dba9 /test/run-tests.sh | |
| parent | verify: this spine still produces this abstraction? (diff) | |
test: database to pod to artefacts
The acceptance test for the document source claim. Two runs of the
same spine with the same flags over the same document:
- the pod to artefacts and outputs, including database, and
- that run's database back to a pod and on to artefacts and outputs.
diff -r between the two trees must be empty.
One comparison covers the written pod tree with its markup, conf, images
and catalogues, the .ssp files, the database itself, the digests, and
the text, html and epub built from them. 690 files for live-manual, ten
languages and a catalogue tree and no images, and 58 for the wealth of
networks, ten images and one language: the two cover each other's gaps,
and SpineAcceptanceDocs widens the set.
--ocda-verify is asserted separately, before the build. The build would
check the same thing and stop, but asking on its own means a failure
says which claim broke: that the pod comes back, or that the abstraction
it makes is the one recorded with it.
The pod for the first run is copied out of the sample set rather than
read where it lies. Read in place it has a site configuration above it
and a materialised pod has none, and the site url reaches the generated
index pages: five files differing in a url, and nothing else, which
would read as corruption.
Both runs ask for the same flags, the dom structure tags the .ssp
records being computed only when an action needs them.
The archive is not compared. Neither run writes one: it is a container
around bytes compared here already, and its own bytes are not part of
what a database claims to carry.
(assisted by Claude-Code)
Diffstat (limited to 'test/run-tests.sh')
| -rwxr-xr-x | test/run-tests.sh | 11 |
1 files changed, 10 insertions, 1 deletions
diff --git a/test/run-tests.sh b/test/run-tests.sh index 4d950dc..615c64f 100755 --- a/test/run-tests.sh +++ b/test/run-tests.sh @@ -23,7 +23,8 @@ # 3 test-abstraction-db.sh the two serialisations agree # 4 test-abstraction-db-roundtrip.sh the .db can be read back whole # 5 test-ocn-alignment.sh the languages agree on their ocns -# 6 test-epub-validity.sh the epubs a reader can actually open +# 6 test-acceptance-db-to-pod.sh a database gives its document back +# 7 test-epub-validity.sh the epubs a reader can actually open # # None of them calls another, and each can be run on its own. The order # matters only for reading the result: @@ -42,6 +43,13 @@ # translations and reports nothing about the other documents. It will # fail if those translations are mended, which is the right moment to # hear about it. +# - 6 is the acceptance test for the document source claim, and the widest +# of them: it builds a document from its pod and again from the database +# that build produced, and requires the two output trees to be identical. +# Where 3 and 4 check one serialisation against another, this checks a +# whole document through the whole pipeline twice. If it fails and the +# others pass, what broke is the carrying or the materialising rather +# than the abstraction. set -e @@ -68,6 +76,7 @@ test-abstraction-ssp-roundtrip.sh test-abstraction-db.sh test-abstraction-db-roundtrip.sh test-ocn-alignment.sh +test-acceptance-db-to-pod.sh test-epub-validity.sh" PASSED=0 |
