I already know using the isTrue
and isFalse
matchers can make test assertions more descriptive and easier to read. However, I want to know if there are any other benefits or reasons for using them instead of boolean values.
expect(actual, isTrue);
expect(actual, isFalse);
vs.
expect(actual, true);
expect(actual, false);
There is no meaningful behavior difference, it is strictly a style choice. The choice exists for legacy reasons - it is not an intentional design for the library.
There is an insignificant difference in the output when it fails: "Expected: <true>" vs "Expected: true".