Bbt – Black Box Testing Directly from Your Documentation

Name: Bbt – Black Box Testing Directly from Your Documentation
Availability: InStock
Author: LionelDraghi

by LionelDraghi·Feb 20, 2026·3 points·0 comments

Visit Project View on HN

AI Analysis

●●SolidBig BrainNiche Gem

Tests live in README as plain English; clever partial parsing eliminates Gherkin boilerplate overhead.

Strengths

•Genuinely novel constraint: documentation IS the test spec, eliminating duplication between README examples and test suites
•Partial English parsing removes ceremony—'When I run gcc' works without strict keyword overhead like pure Gherkin requires
•Ada implementation with Ada Crate of the Year award shows production rigor and niche credibility

Weaknesses

•Tiny audience: CLI tool developers are a fraction of testers; ignores web/mobile/API testing entirely
•No integration with mainstream CI systems shown; unclear how it fits into GitHub Actions/GitLab Pipelines workflows

Post Description

bbt is an open-source tool that lets you test command-line executables using plain Markdown documentation—no scripts, no glue code. Write your specs, run them as tests.

Why bbt? - Zero duplication: Test scenarios live in your READMEs, user guides, or any Markdown file. - Natural language: Steps like When I run gcc --version → Then the output contains 14.2.0 just work. - No learning curve: Partial parsing means you write almost-normal English; bbt extracts the test logic.