I've seen test runners that report the number of assertions checked, not just the number of tests. Is this useful?
I understand if you have non-fatal assertions (like EXPECT_TRUE in googletest), but I think this is a rare feature in testing libraries.
Related Posts
Assertions are a surprisingly nuanced design space. In a test, if I assert `x < y`, I really want to see the values of x and y when it fails.
Do you define an API for every possible predicate (Python's assertLess, expect.js) or try to support the native syntax (c.f. pytest)?
@krinkle A surprising number of PL design workarounds are "just add another equals sign" 🙃
I love how the CommonMark Spec has a test suite that's just a JSON array. It's really easy to test a library for compliance, and I've seen developers nerd-sniped into full compliance.
https://spec.commonmark.org/0.31.2/spec.json