Skip to content

refactor: use expectations for t.throws #1213

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.

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
merged 1 commit into from
Apr 8, 2025
Merged

Conversation

nfischer
Copy link
Member

@nfischer nfischer commented Apr 8, 2025

No change to logic. This is a small refactor to use stricter "expectation" arguments for calls to t.throws().

No change to logic. This is a small refactor to use stricter
"expectation" arguments for calls to t.throws().
Copy link

codecov bot commented Apr 8, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.37%. Comparing base (dbac0a7) to head (2b9dfd1).
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1213   +/-   ##
=======================================
  Coverage   97.37%   97.37%           
=======================================
  Files          35       35           
  Lines        1410     1410           
=======================================
  Hits         1373     1373           
  Misses         37       37           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@nfischer nfischer merged commit ffdd60b into main Apr 8, 2025
20 checks passed
@nfischer nfischer deleted the refactor-assert-throws branch April 8, 2025 06:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant