[ https://issues.jboss.org/browse/RF-13130?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13130: --------------------------------- Hamcrest-style API provides more readable tests, but more importantly results - compare: {code} Assert.assertTrue(list.isEmpty()); {code} Fails with: {{AssertionError}} {code} Assert.assertTrue("list is empty", list.isEmpty()); {code} Fails with: {{list is empty}} {code} Assert.assertThat(list, is(empty()); {code} Fails with: {{The 'list' is expected to be empty, but it was: ...}} ---- The second option is refactoring proof, as it does not have to bear any message in order to understand what assertion has been made. Both APIs are part of JUnit, since JUnit transitionally depends on Hamcrest Core, however in Hamcrest Core are just simple matchers, e.g. it misses: {code} Assert.assertThat(someString, containsString("foo")); {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira