[bluGill]

The fact that gherkin can be be turned into an automated test is a side effect. The real purpose is to get non-programmers to put their requirements in a rigorous form so that programs can implement the spec and know it will do what is intended.

I have never seen it work in practice, but that what it is supposed to be about. If your managers are not looking at the gherkin and making suggestions then there is no point in doing it.

[abracadabra_]

I'm a big fan of the Gherkin syntax and the output of my Example Mapping sessions is generally a big pile of them.

Automated tests are then written based on these but not "using" these. By not "using" the Gherkin scenarios for our tests we can be looser with the language and not have to worry about RegEx.

If a manager, or other non-coder, wants to see the tests, they can look at the very pretty report that was generated.