[Epic] Test DefraDB

[AndrewSisley]

This issue hosts stuff we think we would like to have in order to be satisfied with the correctness of DefraDB at the time of release 1.0.0. The stuff listed here is highly dynamic and I would encourage people to add items regardless of how thought-out they might be. Once we are fairly certain that we do want a thing for/before 1.0.0 that thing should be in issue or SIP format, otherwise inline/plain-text is good enough.

Tasks

Preview Give feedback

1. Document explaining how Source systems are tested docs.source.network#112
   +0
2. +95% line code coverage
3. Stabilize benchmark results #324
   ci/build perf +2
4. Benchmark: External tooling #73
   perf +1
   
5. Nightly CI #197 (issue currently includes benchmarking and cross-platform testing)
6. Basic fuzz testing
7. Long-life testing, ensuring DefraDB doesn't fall over after X hours/days/etc (availability metric? Like benchmarking this is a common thing and we should try and stick to common practises/measurements)
8. Some kind of large-scale randomized P2P resilience testing (chaos monkey-like?)
9. Some kind of chaos monkey-like datastore testing, ensuring very bad things dont happen when unexpected file-system stuff happens
10. Try and come up with means to protect against introducing local stuff into global data areas #1238
    area/db-system area/testing +2
11. Test against multiple Go versions in CI #321
    ci/build +1
12. Introduce proactive test suite #2545
    area/testing +1