Start Here

Welcome to the Bitcoin QA Checklist OS — 152 pre-built test scenarios that tell you exactly what to test before you launch a Bitcoin product. The companion Integration QA Guide explains the why behind every test in plain English.

Set it up in 4 steps

1. Open the Test Cases database below — it is already filled with all 152 tests.
2. Click the Critical-only view — your launch gate. Nothing ships until every Critical test passes.
3. As you run each test, set its Status: Passing, Failing, or Skipped.
4. When you are ready to release, open the Release Gate page and check every box.

<aside> 💡

Priorities: Critical = hard launch gate, a failure here can lose money, do not ship. High = should pass before real volume. Medium and Low = housekeeping and polish. Start with the Critical-only view, get it green, then widen.

</aside>

<aside> 💡

Automate these: every test marked Automatable = Yes can be run for you by the Bitcoin Merchant Test Kit. The IDs match — LN-007 (expired Lightning invoice) is the same test the Kit automates against BTCPay, Alby, OpenNode, and Strike. Filter to Automatable = Yes, then let the Kit handle them.

</aside>

Run a release

• [ ] Every Critical test is Passing
• [ ] Failures are logged as Bugs with txid, payment hash, and channel ID
• [ ] The Release Gate is checked top to bottom
• [ ] No Critical unchecked means cleared to ship

Go further: automate the machine-runnable tests with the Bitcoin Merchant Test Kit, and learn the why behind every test in the Integration QA Guide.

Bitcoin QA — Test Cases (152)