Ideally, we would let users supply their own parser choice based on the tool they are using for their automation. Currently if a user is not using Behave for automation, there is a chance that the parsers will not match.
Specifically users of pytest-bdd and sphinx-gherkindoc cannot use Feature examples like this:
Feature: A
Examples:
| name |
| abc |
| def |
Scenario: Example scenario
Given a name <name>
...
Perhaps a flag can be added to show which parser to use, or which tool's syntax to support --parser pytest-bdd. In that case everything would be the same, but it would do something with these feature example tables.
rbcasperson
commented
4 years ago
Ideally, we would let users supply their own parser choice based on the tool they are using for their automation. Currently if a user is not using Behave for automation, there is a chance that the parsers will not match.
Specifically users of
pytest-bddandsphinx-gherkindoccannot use Feature examples like this:Perhaps a flag can be added to show which parser to use, or which tool's syntax to support
--parser pytest-bdd. In that case everything would be the same, but it would do something with these feature example tables.