Yup, this seems like part of C++11 that needs to be added to the mocks. What's the data type of result in the code you posted? I'll add that to a unit test.

I will add nullptr and assertNull(result)

Those updates still do not fix the issue with assertEqual. The problem is that onAssert tries to print the argument of type nullptr which it is not able to. There needs to be an additional unit test:

unittest(nullpointer_equal)
{
  int* myPointer = NULL;
  int **notNullPointer = &myPointer;
  assertEqual(nullptr, myPointer);
  assertNotEqual(nullptr, notNullPointer);

#if 0
  // The following should not compile, which they currently do not but in a
  // cryptic way. If possible and with low effort an explicit denial which
  // produces an explanatory error would be nice.
  assertLessOrEqual(nullptr, myPointer);
  assertMoreOrEqual(nullptr, notNullPointer);
  assertLess(nullptr, myPointer);
  assertMore(nullptr, notNullPointer);
  assertFalse(nullptr);
  assertTrue(nullptr);
  assertAnyLhsRhsFunction(..., nullptr);
#endif
}

Thanks, those unit tests are exactly what was needed.

@hlovdal You gave me an excellent idea here.

I've set up a new branch called tdd (https://github.com/ianfixes/arduino_ci/tree/tdd). If you can write unit tests that show a problem, make a PR using the tdd branch as a base. That will give me something to work from when I go about fixing the issue, and not require me to break the master branch in the process.

This fix is live in the latest version, sorry for the arbitrary delay there