[Feature]: Run a test directly from a .feature file

[andre-ribeiro-almeida-alb]

Question

This is more of a quality of life issue.

You can find this button on IntelliJ, when using cucumber as the test runner:

There is a similar runner button on vscode, but can only be run from the playwright test.

Is there a way to configure this sort of button in the .feature files when using playwright-bdd?

[vitalets]

Running directly from feature file is not possible now.
The recommended flows:

• using Playwright UI mode
• or run from the generated file:
  

To run directly from feature file we need to adopt IDE extensions that provide this functionality.
Btw, in IntelliJ is it a built-in functionality?

Related to: #178

[andre-ribeiro-almeida-alb]

In IntelliJ it seems to be from the jetbrains gherkin plugin.

Edit:
Even though the button seems to be from the gherkin plugin, I can only actually run the tests with the cucumber for java plugin

[vitalets]

Even though the button seems to be from the gherkin plugin, I can only actually run the tests with the cucumber for java plugin

Does it support JavaScript as well?

[andre-ribeiro-almeida-alb]

Does it support JavaScript as well?

Cucumber-js does, but it is exclusively an IntelliJ Ultimate plugin.

[alescinskis]

Interested in this as well

[vitalets]

Creating a full-featured IDE extension to run & debug tests would be a complex task.
I have an alternative idea: what if we allow to navigate to generated Playwright file from feature file by ctrl+click? From there you can run the particular scenario via Playwright's native plugin.
What do you think?

[andre-ribeiro-almeida-alb]

That is a valid approach, and easy to setup. I believe it's just adjusting the cucumberautocomplete.steps config in .vscode/settings.json file.
However you might be trading off an already existing link to the steps definition, which is also valuable.

[vitalets]

That is a valid approach, and easy to setup. I believe it's just adjusting the cucumberautocomplete.steps config in .vscode/settings.json file. However you might be trading off an already existing link to the steps definition, which is also valuable.

No exactly. Cucumber autocomplete navigates to step definitions by click on step, but I expect to navigate to the generated test by click on scenario.

[andre-ribeiro-almeida-alb]

Oh alright. It seems like a good solution for now.
However I'm not sure how to configure that. As it says here, it might need to be supported by the language itself.

[vitalets]

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

[Rohit5688]

I have created onr extension BDD Test Runner. Use it and let me know in case of any issue