From 114c51ca257cd1b7632d3eeb788dab23d07cb804 Mon Sep 17 00:00:00 2001 From: JohnnyT Date: Wed, 30 Sep 2026 05:23:45 -0600 Subject: [PATCH] Says MapTest's graphs regenerate from the Map MapTest's moduledoc said the two teaching documents' graphs are what the reference host's map answered before it moved into the package. The library loan's graph has since been regenerated from the package's own StatifierBlocks.Map when a timed wait gained the clock mark, so it differs from the host's by that one mark. The moduledoc now says the graphs began as the host's answer, are regenerated from the package's Map when what it answers changes, and names the one difference, as MapFixtures' moduledoc already does. Test prose only; no changelog fragment (changelog.d/README.md excludes tests). Gate: full mix quality green on this exact staged tree (3,954 of 3,954 tests, 95.3% coverage, dialyzer and credo clean). Refs: sb-pgsm --- test/statifier_blocks/map_test.exs | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/test/statifier_blocks/map_test.exs b/test/statifier_blocks/map_test.exs index 9ed36e5e..32f7b3e3 100644 --- a/test/statifier_blocks/map_test.exs +++ b/test/statifier_blocks/map_test.exs @@ -3,7 +3,14 @@ defmodule StatifierBlocks.MapTest do The Map's graph, read without laying it out: it is the document, every empty slot is marked, the options that keep the model order are where the moduledoc says they are, and for the two teaching documents it is - what the reference host's map answered before it moved here. + the graph checked in under `test/fixtures/map/`. + + Those graphs began as what the reference host's map answered before it + moved here; since then a change to what the package's own + `StatifierBlocks.Map` answers regenerates them from it. The library + loan's graph was regenerated when a timed wait gained the clock mark, + and differs from the reference host's by that one mark on its loan + period (see `StatifierBlocks.MapFixtures`). """ use ExUnit.Case, async: true