assertEquals from assert_macro.h actually is assertTrue

assertEquals would need two have two parameters, not just one.

// misnomer:
assertEquals( (0+0) == 0 )
// should be:
assertTrue( (0+0) == 0 )

// assertEquals I would expect to call
// providing both the expected value and the actual value:
assertEquals( 0, (0+0) )

Start with assert_macro.h and search for assertEquals usages in the sample project. Check whether the macro is intended to represent a one-argument boolean assertion or a two-argument equality assertion, then inspect any affected examples or tests. Done means the assertion names and parameter behavior match their documented meanings.

Vom Indexierungsmodell aus dem Issue-Text verfasst.