Skip to content

test(litigation): cover slugify, registry fallback, and transcript footer - #122

Draft
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/missing-test-coverage-0990
Draft

test(litigation): cover slugify, registry fallback, and transcript footer#122
cursor[bot] wants to merge 1 commit into
mainfrom
cursor/missing-test-coverage-0990

Conversation

@cursor

@cursor cursor Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Risky behavior now covered

  • slugify: special-character sanitization, empty-input fallback, and length cap for transcript filenames.
  • allocate_case_no without registry: generates a valid case number when case-registry.yaml is missing.
  • save_transcript courtroom location: writes to courtroom/transcripts/ when requested.
  • SCRIBE certification footer: ensures deliberation bodies without a footer receive the canonical certification line.

Test files added/updated

  • tests/test_litigation_run.py — 4 new tests

Why these tests materially reduce regression risk

Recent merges (#54, #66) fixed duplicate case numbers and transcript path resolution. These tests extend that coverage to adjacent edge cases in the same runner module — filename slug collisions were already covered; slugify/registry/courtroom-path/scribe-footer were not.

Validation

  • pytest tests/64 passed
Open in Web View Automation 

…oter

Add regression tests for litigation runner edge cases: slug sanitization,
case-number allocation without a registry file, courtroom save location,
and automatic MORNINGSTAR::SCRIBE certification footer.

Co-authored-by: exios4 <exios4@protonmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant