You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When launched through io.cucumber.core.cli.Main Cucumber will use cucumber.properties. When launched through the JUnit Platform the junit-platform.properties file is used.
This difference can be confusing for novice and advanced users who use Intelij IDEA. And unfortunately JetBrains has made little progres improving on this (see IDEA-227508).
✨ What's your proposed solution?
Create a new main method that maps the CLI arguments to the JUnit Platform and runs Cucumber. This main can then be used in IDEAs run configuration.
⛏ Have you considered any alternatives or workarounds?
Reading cucumber.properties in the JUnit Platform is an option. Though because Cucumber and JUnit have different semantics around merging properties this doesn't seem feasible.
Alternatively Cucumber could change it's property reading mechanism to be more sane. But that would be something for the next major release.
Or I could implement a better Cucumber plugin. Though I should probably do it in VS Code. Maybe that will get JetBrains attention. My subscription certainly doesn't.
The text was updated successfully, but these errors were encountered:
Additional idea. Consider adding a --junit-platform flag or subcommand to the regular CLI that will delegate to the JUnit Platform for reduced friction.
🤔 What's the problem you're trying to solve?
When launched through
io.cucumber.core.cli.Main
Cucumber will usecucumber.properties
. When launched through the JUnit Platform thejunit-platform.properties
file is used.This difference can be confusing for novice and advanced users who use Intelij IDEA. And unfortunately JetBrains has made little progres improving on this (see IDEA-227508).
✨ What's your proposed solution?
Create a new main method that maps the CLI arguments to the JUnit Platform and runs Cucumber. This main can then be used in IDEAs run configuration.
⛏ Have you considered any alternatives or workarounds?
Reading
cucumber.properties
in the JUnit Platform is an option. Though because Cucumber and JUnit have different semantics around merging properties this doesn't seem feasible.Alternatively Cucumber could change it's property reading mechanism to be more sane. But that would be something for the next major release.
Or I could implement a better Cucumber plugin. Though I should probably do it in VS Code. Maybe that will get JetBrains attention. My subscription certainly doesn't.
The text was updated successfully, but these errors were encountered: