pytest-bdd parse step definition matcher

[kieran-ryan]

🤔 What's changed?

• Support the parse step definition matcher of pytest-bdd - which is also used by behave; both Python frameworks

⚡️ What's your motivation?

• Closes Pytest-BDD parse matcher step definitions #205.

🏷️ What kind of change is this?

• ⚡ New feature (non-breaking change which adds new behaviour)

♻️ Anything particular you want feedback on?

📋 Checklist:

• I agree to respect and uphold the Cucumber Community Code of Conduct
• I've changed the behaviour of the code
  • I have added/updated tests to cover my changes.
• Users should know about my change
  • I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

---

This text was originally generated from a template, then edited by hand. You can modify the template here.

[neskk]

Hello @kieran-ryan,

Found some time to help test this PR.

• I've added some pytest-bdd parser step definitions to the StepDefinitions.py test file, but I have the ExpressionBuilder tests failing.

  79 passing (1s)
  22 failing

  1) ExpressionBuilder
       with NodeParserAdapter
         builds parameter types and expressions from tsx source:

      AssertionError [ERR_ASSERTION]: Expected values to be strictly deep-equal:
+ actual - expected

+ []
- [
-   'a {uuid}',
-   'a {date}',
-   'a {planet}',
-   /^a regexp$/,
-   "the bee's knees"
- ]

• Since my node/vs-code development experience is very limited, I don't know what's the best procedure to test this or contribute with unit-tests. I would appreciate some help. Will the support for this kind of pytest-bdd syntax be hard to merge?