They claim to run that test on any changes but in fact might not be testing anything at all according to this footnote in the Jepsen report:

> RavenDB’s Jepsen test may not have measured anything at all: at least in the most recent revision, the generator included no client operations of any kind.

Remember folks, if you can't get your test to fail by intentionally breaking the implementation, you don't have a test.

Tickets related to this report from Aphyr: - https://github.com/ravendb/ravendb/issues/17928 - https://github.com/ravendb/ravendb/issues/17927