About h2check
A reference for people who test software. Every page answers one question of the form “how do I check X”, and answers it with commands that were run rather than described.
Why it exists
Vendor documentation tells you what a flag does. It rarely tells you what the output looks like when the thing you are testing is broken, which is the moment a tester actually needs help. That gap is what these pages fill: the real output, the threshold with its source, and the failure that the documentation never mentions.
Scope
440 procedures across 21 areas of the stack. The list grows only where people are searching for a check, and never to round out a category.
Who writes it
Maks Verny
Founder and principal QA automation engineer. Test automation engineer and QA architect with 8 years in the software industry. Builds CI/CD pipelines, tests web application security, verifies APIs and analyses performance. Founder of h2check.org, a set of verification procedures for QA engineers, testers and developers.
How to read a page
The highlighted paragraph under the heading is the whole answer in about fifty words. Everything below it is for the case where that is not enough: the steps, the output, the table that maps what you see to what to do, and the mistakes that make a passing check look like a failing one.
The rules the pages are held to are on the methodology page.