diff options
Diffstat (limited to 'test/test_temporal_ef.ml')
| -rw-r--r-- | test/test_temporal_ef.ml | 14 |
1 files changed, 12 insertions, 2 deletions
diff --git a/test/test_temporal_ef.ml b/test/test_temporal_ef.ml index 4e97d33..4995ee1 100644 --- a/test/test_temporal_ef.ml +++ b/test/test_temporal_ef.ml @@ -526,8 +526,18 @@ let test_christmastide_feria_slugs () = itself uses 3 January and 10 January below instead -- both, checked directly against data/ef/sanctoral.sexp, have no competing entry in any year, so the BVM Saturday office genuinely IS reachable there. *) - Alcotest.(check string) "26 Dec (Sat)" "ef-christmas-0-saturday" (slug_of (d 2026 12 26)); - Alcotest.(check string) "28 Dec (Mon)" "ef-christmas-0-monday" (slug_of (d 2026 12 28)); + (* CORRECTED 2026-08-18: these pinned "ef-christmas-0-<weekday>", the generic + Christmastide ferial slugs 26-28 December used to fall through to. Those + are days WITHIN the Octave of the Nativity (RG 67, "Dies infra octavam + sunt II classis") and now carry the octave-day slug exactly as 29-31 + always did -- which is what gave M11's missing "Com. octavae Nativitatis" + a candidate to be commemorated over. The days are still Saturday and + Monday; only the temporal identity changed, and only because it was + wrong. *) + Alcotest.(check string) "26 Dec (Sat): day 2 within the Octave" "ef-nativity-octave-day-2" + (slug_of (d 2026 12 26)); + Alcotest.(check string) "28 Dec (Mon): day 4 within the Octave" "ef-nativity-octave-day-4" + (slug_of (d 2026 12 28)); (* 3 Jan 2026 is a SATURDAY, genuinely reachable (data/ef/sanctoral.sexp has no 3 January entry) -- the real demonstration for the "-1-" stretch that 26 December's own Saturday could not honestly provide. *) |