Skip to content
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

fix: Assert.assertThrows() should check result of exceptionConsumer #135

Merged
merged 3 commits into from
Nov 30, 2023

Conversation

javeme
Copy link
Contributor

@javeme javeme commented Nov 26, 2023

No description provided.

Copy link

codecov bot commented Nov 26, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (5ad55fb) 93.15% compared to head (68b359e) 93.15%.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #135   +/-   ##
=========================================
  Coverage     93.15%   93.15%           
  Complexity       65       65           
=========================================
  Files             9        9           
  Lines           263      263           
  Branches         22       22           
=========================================
  Hits            245      245           
  Misses            8        8           
  Partials         10       10           

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

@javeme
Copy link
Contributor Author

javeme commented Nov 26, 2023

+ @zhenyuT

@zhenyuT
Copy link
Contributor

zhenyuT commented Nov 26, 2023

Seems there's no need to use CompletableFuture in assertThrows method?

simon824
simon824 previously approved these changes Nov 30, 2023
@simon824 simon824 merged commit 8c93652 into master Nov 30, 2023
9 checks passed
@simon824 simon824 deleted the assert-throws-bugfix branch November 30, 2023 08:25
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.

4 participants