Skip to content
This repository has been archived by the owner on Dec 18, 2019. It is now read-only.

tagExpression vs tags for scenario filtering #132

Open
gasparnagy opened this issue Jun 26, 2018 · 0 comments
Open

tagExpression vs tags for scenario filtering #132

gasparnagy opened this issue Jun 26, 2018 · 0 comments

Comments

@gasparnagy
Copy link

The Cucumber.js CLI API has been using the --tagExpression option to filter the scenarios to be executed.

The API has been changed (in v4?), and it is using the more clean (?) --tags option for the same filtering. (see https://github.com/cucumber/cucumber-js/blob/master/docs/cli.md#tags)

The wdio-cucumber-framework has been using a similar option (tagExpression) for the filtering that has been also changed to tags (intentionally?). In the current released version (v2.1.0), the filtering has to be done like that.

The merged PR #127 reverts the setting back to tagExpression and I was wondering if this is really good or not. What is better: keeping the compatible setting (tagExpression) but get out of sync with cucumber.js or make the breaking change and be in sync with cucumber.js...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant