Skip to content

Commit 95af976

Browse files
committed
Add "Deprecate Assert#assertThat"
We forgot to add this changes to the release notes. Fixes #1645.
1 parent 2df7e08 commit 95af976

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

doc/ReleaseNotes4.13.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,10 @@ To ensure serializability of further changes in `ArrayAssertionFailure` (until e
2626

2727
<a name="1315-f2">[2]</a> [Case](https://github.com/junit-team/junit4/pull/1315#issuecomment-222905229) if the test class is compiled with <= v4.11, where only `fCause` is initialized and not `Throwable#cause`, it can now fallback to the field, `fCause`, when building the message.
2828

29+
### [Pull request #1150:](https://github.com/junit-team/junit4/pull/1150) Deprecate `Assert#assertThat`
30+
31+
The method `assertThat` is used for writing assertions with Hamcrest. Hamcrest is an independent assertion library and contains an own `assertThat` method in the class `org.hamcrest.MatcherAssert`. It is available both in the old Hamcrest 1.3 release and in the current Hamcrest 2.1. Therefore the JUnit team recommends to use Hamcrest's own `assertThat` directly.
32+
2933
# Test Runners
3034

3135
### [Pull request #1037:](https://github.com/junit-team/junit/pull/1037) `BlockJUnit4ClassRunner#createTest` now accepts `FrameworkMethod`

0 commit comments

Comments
 (0)