Skip to content

Says MapTest's graphs regenerate from the Map #683

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
johnnyt merged 1 commit into from
Sep 30, 2026
Merged

Says MapTest's graphs regenerate from the Map #683

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion test/statifier_blocks/map_test.exs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
Loading