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
In JUnit 4.13 ExpectedException is deprecated. The replacement, assertThrows, is Java 8-centric and would be annoying to use in the short-term. Using try+fail would increase boilerplate and would be worse than just using ExpectedException.
We can @SuppressWarnings for now, but we should swap to assertThrows (or Truth's variant) in the future once we can use Java 8 in our tests.
The text was updated successfully, but these errors were encountered:
ExpectedException is deprecated, so I fixed the new warnings. However,
we are still using ExpectedException many places and had previously
supressed the warning. See
grpc#7467 . I did not fix those
existing instances that had suppressed the warning, since it is
unrelated to the upgrade and we have been free to fix them at any time
since we dropped Java 7.
ExpectedException is deprecated, so I fixed the new warnings. However,
we are still using ExpectedException many places and had previously
supressed the warning. See
#7467 . I did not fix those
existing instances that had suppressed the warning, since it is
unrelated to the upgrade and we have been free to fix them at any time
since we dropped Java 7.
In JUnit 4.13 ExpectedException is deprecated. The replacement,
assertThrows
, is Java 8-centric and would be annoying to use in the short-term. Using try+fail would increase boilerplate and would be worse than just using ExpectedException.We can
@SuppressWarnings
for now, but we should swap to assertThrows (or Truth's variant) in the future once we can use Java 8 in our tests.The text was updated successfully, but these errors were encountered: