-
-
Notifications
You must be signed in to change notification settings - Fork 698
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
An easier way to use a different langauge #24
Comments
Hi @esdoppio There isn't currently a way to specify a language globally, but I really like your idea. It sounds like the lack of this feature really bothers you. Don't worry - Cucumber is open source, so you can fix this yourself. Just fork the repo, add support for a new Thanks! |
Thanks for the reply. If we're really going this direction, I think the Do you think this is over-designed? And what do you think of the idea of a configuration file (for cucumber)? @aslakhellesoy |
I agree that a Cucumber already has a configuration file - Luckily Gherkin already supports specifying a default language - it's just a matter of hooking into it. See cucumber/gherkin#78 |
@esdoppio which flavour of Cucumber are you using? |
@mattwynne It's cucumber-ruby. |
OK, in that case let's start with an issue over there: https://github.com/cucumber/cucumber-ruby/issues Can you raise one, and do your best to describe your acceptance criteria? The very best thing would be if you could create a PR with a new failing feature in https://github.com/cucumber/cucumber-ruby/tree/master/features/docs/cli |
I'm closing this issue since it's in the wrong repo. |
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. |
Say I need to use Japanese as the primary language for my feature files. Do I need to actually put
at top of each file? That's not really smart to do to be honest.
Can't find a cli option that specifies a spoken language when running tests, and the reference doesn't say anything about this.
The text was updated successfully, but these errors were encountered: