We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If no allureConfig.json with tag patterns specified in it, all gherkin tags are converted to Allure tags.
We should provide reasonable defaults. For example, we might convert allure.suite:My-suite to the label suite=My-suite.
allure.suite:My-suite
suite=My-suite
The motivation is to make the tags API of Allure SpecFlow usable without configuration.
That will be a breaking change. We might provide a feature switch in allureConfig.json for those who don't want default patterns for some reasons.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm submitting a ...
What is the current behavior?
If no allureConfig.json with tag patterns specified in it, all gherkin tags are converted to Allure tags.
What is the expected behavior?
We should provide reasonable defaults. For example, we might convert
allure.suite:My-suite
to the labelsuite=My-suite
.What is the motivation / use case for changing the behavior?
The motivation is to make the tags API of Allure SpecFlow usable without configuration.
Please tell us about your environment:
Other information
That will be a breaking change. We might provide a feature switch in allureConfig.json for those who don't want default patterns for some reasons.
The text was updated successfully, but these errors were encountered: