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

v. 0.9.0: Setting the default language in the Cucumber builder is not applied during test execution #126

Closed
florianrein opened this issue Aug 25, 2021 · 2 comments
Labels
bug Something isn't working
Milestone

Comments

@florianrein
Copy link

florianrein commented Aug 25, 2021

Prereqs

  • 2 Feature Files doing exactly the same, but one is using default Gherkin keywords in English, and one uses German keywords
  • the latter has the magic comment: # language: de
  • .language("de") is set in the creation of the runner

Steps to reproduce

  1. cargo clean
  2. cargo test

Actual Result
Both feature files are executed.

Expected Result
An error message should be thrown stating that the keywords in the English feature file could not be evaluated.


Hi Brendan, Hi Fellows,
while doing a writeup about the changes since the 0.8 release, I conducted the above experiment.
In the process I noticed that the .language("de") call seems not to be applied.
Am I missing something or do we have an actual bug?
My full code is located here.
The relevant files are ./features/* and cucumber.rs .

@bbqsrc
Copy link
Member

bbqsrc commented Sep 16, 2021

Probably a bug. Hope to look at it soon, a bit of a strange regression that one.

@tyranron tyranron added the bug Something isn't working label Sep 27, 2021
@tyranron
Copy link
Member

Fixed in #128

@tyranron tyranron added this to the 0.10 milestone Oct 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants