commit 9532f6b44dccd84c74896acffa54157d8f1ead59
from: Stefan Sperling <stsp@stsp.name>
date: Sun Jul 14 10:20:05 2019 UTC

mention C tests in README for completeness

commit - 42620da7ca2255a163e39fae8d9f618df25fdec6
commit + 9532f6b44dccd84c74896acffa54157d8f1ead59
blob - 733bcb57e095441b2043ea7b78d87eab2ed70424
blob + dedfae24ae7a152b9e983e8daa341e38b6ab12fe
--- README
+++ README
@@ -54,6 +54,11 @@ in writing a regression test saves time wasted on back
 about how the problem can be reproduced. A regression test will need to be
 written in any case to verify a fix and prevent the problem from resurfacing.
 
+It is also possible to write test cases in C. Various examples of this
+exist in the regress/ directory. Most such tests are unit tests written
+before got's command line interface was available; it is unlikely that a
+problem found during regular usage will require a test to be written in C.
+
 Some areas of code, such as the tog UI, are not covered by automated tests.
 Please try to find a way to trigger your problem via the command line before
 reporting the problem without including a written test case. If writing an