You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CI review surfaced two refinements:
1. Endpoint bands like `11.0 <= ci_low <= 11.6` would still pass values
rounding to several different one-decimal displays (11.0, 11.1, ...,
11.6) while the notebook prose stays at "11.3", "12.8", "11.4",
"13.3", "11.5", "13.6". Replace those with `round(ci_low, 1) == 11.3`
etc. - directly pins the displayed rounding so any drift past the
tenth fails the test.
2. The warning tests didn't pin the notebook's full warning contract.
`event_study_results` suppressed A7 for fixture cleanliness while
the docstring claimed "A7 visible". Two changes:
- Fix the fixture docstring to acknowledge A7 is muted there for
value-checking tests, with the notebook's actual warning-policy
contract validated separately
- Add `test_event_study_warning_policy_matches_notebook` that
mirrors the notebook's exact filter (only matmul-pattern
RuntimeWarnings silenced) and asserts the resulting warning set:
exactly one UserWarning (A7 leavers-present, the one the markdown
explains) and zero RuntimeWarnings. If a future library change
emits an unexpected warning on this code path, the test fails.
12 tests pass in ~0.07s (was 11).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments