Vitaliy Potapov

Could anybody suggest any alternatives?

The setup is correct, it should work. Could you check, maybe you have another Cucumber extension enabled, e.g. [this one](https://marketplace.visualstudio.com/items?itemName=CucumberOpen.cucumber-official)?

Yes, it should work for steps with parameters as well. I've checked with exactly the same step name - works for me. My settings.json: ```json { "cucumberautocomplete.steps": ["steps/**/*.ts"] } ```...

If possible - could you try to reproduce your code structure on `decorators` branch in example? I will check in my vscode setup.

@helmutchecker did you try to use that [Cucumber extension](https://marketplace.visualstudio.com/items?itemName=CucumberOpen.cucumber-official) instead of `cucumberautocomplete`? maybe it will handle tsdoc properly. Meanwhile I've updated [docs](https://vitalets.github.io/playwright-bdd/#/guides/ide-integration?id=ide-integration) on conflicting VSCode extensions, thanks for highlighting that.

+1 for playwright-bdd. We are setting `body: ''` for external attachments.

@digitaldoddy thanks for reporting this, I can confirm it's a bug. Definitely, component tests have never worked this way. The root cause lies at the architectural level: 1. Playwright collects...

I've updated docs that component tests are actually not supported: https://vitalets.github.io/playwright-bdd/#/guides/component-tests

> My plan for now is to just serve my component variations using storybook and run Playwright E2E tests on those, which works with playwright-bdd Good idea. Will add it...

> can storybook work ? Yes, it should work. There is no guide for that, but if you try - feel free to share your result or issues.