Audit the Gherkin

A senior BDD review of the file you pasted: one verdict per scenario, the abstraction level, and whether the file speaks the domain's own language.

The feature file — paste it, or drop the .feature nothing pasted yet

Drop a .feature file anywhere in this box, or Read and parsed here. Nothing uploads until you run a lane.

Context the reviewer should have (optional — the domain, the system under test, what worries you)

Step definition language

Also selects the language of the free skeletons below.

The browser's own read — free, no sign-in

Pure computation, not judgement: which keywords are present, whether every <placeholder> has an Examples column, whether the rows are the same width as the header, which steps reduce to the same definition, and where a step describes a control instead of an intent. Free, offline, and the model is required to reconcile its answer against every flag listed here.

Raw reply

How it works

Nothing to paste? — a real-shaped ATM file with a scenario that asserts nothing, an unbound placeholder, a ragged Examples row, a password in a step and four steps written as clicks. Or see a finished result with no run and no charge: , , , or .

The browser reads it first

A hand-written Gherkin parser builds the AST, runs twenty-nine deterministic rules over it, aligns every Examples table and works out how many step definitions the file actually owes you. That is free, needs no account, and nothing leaves the page.

Pick the lane

Audit it, rewrite it declaratively, hunt the scenarios it never covers, draft the step definitions in your language, or turn it into a manual test plan. Same file, five different jobs — and the lane you pick is priced before you run it.

The answer is held to the parser

Every flag the browser raised is sent with the run and comes back reconciled — confirmed, cleared with a reason, or not assessed. Disagreements are shown, not hidden. The rewritten file is re-parsed and re-linted in front of you before you are allowed to feel good about it.