title: Is org.junit.Assert.assertThat better than org.hamcrest.MatcherAssert.assertThat?
body: <p>I'm new to JUnit and Hamcrest and would like best-practice advice so I can decided which documentation to study first.</p>
  
  <p>For starters, which of these <code>assertThat</code> methods is better?</p>
  
  <ol>
  <li>org.junit.Assert.assertThat (from junit-4.11.jar)</li>
  <li>org.hamcrest.MatcherAssert.assertThat (from hamcrest-core-1.3.jar)</li>
  </ol>
  
  <p>According to one person last year, <a href="http://www.objectpartners.com/2013/09/18/the-benefits-of-using-assertthat-over-other-assert-methods-in-unit-tests/">"JUnit has the assertThat method, but hamcrest has its own assertThat method that does the same thing."</a>.</p>
  
  <p>According to someone earlier this year, Hamcrest <a href="http://blog.code-cop.org/2014/02/assert-or-matcherassert.html">"could potentially give better error messages because the matcher is called to describe the mismatch"</a>.</p>
  
  <p>It's hard to tell which versions of Junit and Hamcrest were compared in those posts.  So I'd like a recommendation based on the most current released versions.</p>