How do you ensure that the log messages contain enough information to be useful without encumbering the development of new code?
Some months ago I started work on a way to test random, valid SQL in CockroachDB. This is important to expose unintended behavior in our server.
This blog post outlines how fuzz testing uncovered a Schrodinbug in CockroachDB, how Go was partly to blame, and how we addressed it using strong typing.
Writing good tests is tricky when the system has a lot of moving parts. In this post we will go over how to outsmart Go dependencies in testing.
We at Cockroach Labs absolutely love Aphyr's work. We are avid readers of the Jepsen series – which some know as high quality reviews of correctness...