Add converter from AsciiDoc to Gherkin

[mojavelinux]

To complement the existing converter (Gherkin to AsciiDoc), it would be helpful to be able to convert from AsciiDoc to Gherkin. Supporting this complementary converter would allow spec definitions to be written in AsciiDoc and converted into executable tests, either once or as part of the automated build pipeline. It would also encourage us to think about the best semantic structure for defining features and related stories in AsciiDoc.

[domgold]

Excellent idea!
I can think of 2 use cases. I have created gists for each of them, so we can discuss the semantic structure:

• one asciidoc file = one feature
• one asciidoc file = many features

Have a look at them and let me know how you think about it.

[mojavelinux]

Personally, I prefer the one AsciiDoc file for one feature (and multiple scenarios). I think it's good to keep features in separate files since that maps well with Gherkin.

I have a repository with a bunch of files in this format (for a client), which I'll point to as soon as the repository gets pushed.