Gherkin

What is it?

Gherkin is a way to write down what your software should do using simple sentences: Given [some starting state], When [something happens], Then [this should happen]. Think of it as a recipe that both you and the computer can read.

Why does it matter?

Instead of a long requirements document that nobody reads, we write short scenarios that double as automated tests. You approve them in plain English — then the computer checks them automatically on every change. What you agreed to is what the software does.

Benefits

For you

Requirements are in plain English. You approve them. The computer checks them automatically. No surprises at launch.

For the build

Executable specifications. Automated acceptance tests. Clear pass/fail on every feature.