sqlite3 test suite by Nelson Minar.
From the post:
I felt guilty complaining about sqlite3’s source distribution, so I went to look at the real source, what the authors work with. It’s not managed by git but rather in Fossil (an SCM written by the sqlite3 author). Happily the web view is quite good.
One of the miraculous things about sqlite3 is its incredible test suite. There are 683,932 lines of test code. Compare to 273,000 lines of C code for the library and all its extensions. sqlite3 has a reputation for being solid and correct. It’s not an accident.
The test size is overcounted a bit because there’s a lot of test data. For instance the test for the Porter Stemmer is 24k lines of code, but almost all of that is a giant list of words and their correct stemming. Still very useful tests! But not quite as much human effort as it looks on first blush.
…
Just a quick reminder that test suites have the same mixture of code and data subjects as the code being tested.
So your software passes the test. What was being tested? What was not (the weird machines input) being tested?
If you don’t think that is a serious question, consult the page of SQLite vulnerabilities.
I saw this in a tweet by Julia Evans.