-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for RuntimeOptions.merge and multiple @CucumberOptions #608
Comments
Currently there is an inconsistency with respect to how the option types that can have multiple value (tags, features, glue) are "merged" when defined in more than one place. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in a week if no further activity occurs. |
This issue has been automatically closed because of inactivity. You can support the Cucumber core team on opencollective |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Currently, the expectation is that there may be only one class annotated with CucumberOptions.
This is a bit limiting - specifically, with Android and running from Eclipse, there is not a good way to specify alternative options, without changing the ones already defined. This is needed in cases where a developer may want to use specific options while working on a task, for example, without modifying the project default CucumberOptions.
The suggestion here is to support multiple classes annotated with CucumberOptions. Then, all of them are merged, in order. This will also require ability to specify CucumberOptions merge order.
Merging here means overwrite the option if it already exists (was specified previously).
The text was updated successfully, but these errors were encountered: