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.
miniblog.
Related Posts
I'm adding a += operator to my programming language, because writing `x = x + 1` is tedious.
This opens the tricky design question of which operators should support this. Is += and -= sufficient, or do you expect things like >>= and **= to be available?
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)?
As Rust grows in popularity as a systems language, I expect that someone will develop a dynamic language explicitly designed with great interop in mind.
C++ games seem to use Lua for this, and I've seen Java projects use Groovy.
Are there any up-and-coming contenders for Rust?