Vitaliy Potapov

Yes, we need a separate playwright-bdd-vscode extension for that.

> I have created onr extension [BDD Test Runner](https://marketplace.visualstudio.com/items?itemName=rohitsakhawalkar.playwright-bdd-lens). Use it and let me know in case of any issue That's very interesting, I'll check! Note: on the VSCode extension...

I took a quick look — it should work out of the box. Could you try setting the API key in the Playwright config, as [shown here](https://docs.appetize.io/testing/test-configuration#test-android-and-ios-apps)?

I've tried to reproduce the setup on the example repo, for me it works. Could you please check out [merge-reports-issue-320](https://github.com/vitalets/playwright-bdd-example/tree/merge-reports-issue-320) branch and adopt it deeper to your case. What I...

Maybe also re-structure reporters to have better visibility what reports where, something like ```ts const commonReporters: ReporterDescription[] = [ ... ]; const ciReporters: ReporterDescription[] = [ ... ]; const shardReporters:...

Thanks for repro, I confirm the bug. Actually, the correct `testDir` is provided to the reporting module, but it's not normalized, e.g. `/.features-gen/../some_other_folder`. That's why pw-bdd can't find the project....

Hey @woppa684 Thanks for pointing on that. I agree it could be an issue, but when I tried to reproduce, it works correctly: 1. I've installed all dependencies of [playwright-bdd-example](https://github.com/vitalets/playwright-bdd-example)...

Thanks for the investigation! I also tried the example setup with `pnpm-workspace.yaml` and hoist: true / false - worked for me in both cases. Is it right, that in your...

> 1. Is there a way by which we can have one test.describe for a Feature with each scenario represented as test? This is how it works now. Given a...

Got it, I like the idea. The resulting structure will be simpler. The original structure with `test.describe` for scenario outline allows to run the whole bunch of tests with a...