As discussed with @josef-widder earlier this week and with @marbar3778 and @cmwaters yesterday, it would be helpful, both to the team and users, to have an easy way to know how different aspects of Tendermint are tested, what tests have been run, and what the results of those tests have been (especially for large-scale testnet executions, and for model-based testing).

Some of the work in #8786 touches on this, and this document for Interchain Security is a good example of the structure of the sort of document aimed for here.

The rough overall structure of such a document for Tendermint would be:

1. A list of all QA methods used in the project and when they're used.
2. A table showing concerns vs relevant QA methods for each of those concerns. This could include links to tools or parts of the codebase that perform important/substantial tests (e.g. a link to the model-based tests for the light client).
3. A QA log with dated entries linking to manually executed testnet/MBT/etc. results. The idea here would not be to capture results from any automated testing, as these are assumed to be available via GitHub.