It's oddly frustrating writing tests for a test library. You want better testing features (hence writing the library), but you have to write tests without them (due to bootstrapping.
Related Posts
I'm experimenting with live-evaluating tests in my programming language project.
It's relatively fiddly to hook up a UI for this, but it saves a precious keystroke to run the tests! I'm hoping that it results in more, better tests due to the convenience.
Is there any relationship between language adoption and the size of its standard library?
These days it seems completely orthogonal, but early Java adopters spoke highly of the collections library compared with C++.
Maybe it's the widespread availability of package managers?
Has anyone built a great solution to 'run all my unit tests automatically'?
It's straightforward to write a while loop in bash, but handling timeouts, syntax errors etc well is hard.
Running on save would be good, although I wonder if you could run fast tests on each keystroke.