title: Why assertEquals(a, b) instead of assert(a == b)?
body: <p>Why most (all?) unit test frameworks have large APIs with separate functions for specifying different types of boolean conditions (eg. <code>assertEquals</code>, <code>assertNotEqual</code>, etc) instead of using single <code>assert</code> function (or language construct) with desired boolean expression?</p>