Skip to content
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

Default format for gherkin tags #439

Open
1 of 3 tasks
delatrie opened this issue Dec 4, 2023 · 0 comments
Open
1 of 3 tasks

Default format for gherkin tags #439

delatrie opened this issue Dec 4, 2023 · 0 comments
Labels
task:improvement Change that improves some user experience but can't be considered a new feature theme:specflow

Comments

@delatrie
Copy link
Contributor

delatrie commented Dec 4, 2023

I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

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 label suite=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.

@delatrie delatrie added theme:specflow task:improvement Change that improves some user experience but can't be considered a new feature labels Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task:improvement Change that improves some user experience but can't be considered a new feature theme:specflow
Projects
None yet
Development

No branches or pull requests

1 participant