I appreciate from bottom of my heart for the whole effort put to create this repo : https://github.com/vitalets/playwright-bdd/tree/main getting inspired by issue https://github.com/microsoft/playwright/issues/11975 But .. I had been able to convince my client we can use Playwright - POM model and no need of BDD to be in place. Also I raised, are Business Analysts/Product Owners/Heads keen to go through features written? if this is only needed, I could take a list of test cases written under test.describe()..test()/its pass/failure and send on as updates to any new feature additions. They agreed and no issues at all, able to create Playwright - OpenFin app automation.
It gets complicated when requirements like OpenFin app, electron app come into picture for automation, having numerous subPage layers and also to use BDD ( cucumber ) on top of it.
Just a thought for those looking for BDD or cucumber integration with PW or due to client pressure. Be bold to showcase pros & cons if you are the one starting the framework from scratch.
This thread is trying to answer question "Is it really necessary to integrate Playwright with Cucumber to achieve step definitions via BDD?"
Rayrun is a community for QA engineers. I am constantly looking for new ways to add value to people learning Playwright and other browser automation frameworks. If you have feedback, email [email protected].