Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: tying step text to semantics is tedious—use NLP! #7

Open
jrwdunham opened this issue Aug 16, 2019 · 0 comments
Open

Problem: tying step text to semantics is tedious—use NLP! #7

jrwdunham opened this issue Aug 16, 2019 · 0 comments

Comments

@jrwdunham
Copy link
Owner

It is tedious to have to manually connect each step text/definition, e.g., "Given app has a resource with attribute value", to its execution semantics, e.g., (confirm-existence-of-or-create context resource :attribute value). It should be possible to devise a "step grammar" (CFG) that parses step texts (instead of using simple regular expressions) and maps them to expected function names and definitions. This could be a real "value add" to Gherkin from the Clojure/Instaparse side of things.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant