Skip to content

[Housekeeping] Rationalize tests around dispatch paths #424

Description

@lrnv

Scope

Map the test suite to actual dispatch and numerical paths, then remove redundant family-operation combinations while preserving functional coverage.

The bestiary and generic tests should select representative models for mechanisms such as closed forms, generic Williamson transforms, discrete and continuous frailties, finite support and atoms, integer and fractional orders, conditioning, and numerical quadrature.

Acceptance criteria

  • documented test-to-dispatch-path matrix;
  • distinction between unit, generic contract, and integration tests;
  • deterministic stochastic regressions;
  • duplicate coverage removed only after the same path is covered elsewhere;
  • expensive exceptions replaced by targeted tests only when generic coverage is genuinely disproportionate;
  • before/after test timings reported.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions