-
Notifications
You must be signed in to change notification settings - Fork 609
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
Other languages does not work #44
Comments
You need to add the following to the top of your feature files to use another language,otherwise behat assumes it's in english : language: pt |
i didn't see that in doc's, now is working! i will read again the docs and make a PR with it if the doc's does not mention it ;) |
I had the same problem 2 days ago, see http://groups.google.com/group/behat/browse_thread/thread/93d0ab611e90d7b1 |
But it doesn't make sense, the language is set to "pt" in behat.yml it should work without the reference inside the feature file or not @everzet? |
No it should not. The language, that you specify in Features are explicit pieces of information, that could and should be used separately from Behat in many cases. Keeping this in mind, hiding some important information (like language) from them in Behat configs is the true crime! Also, single project could have features in multiple languages ;-) And english is used by default. |
@everzet you are more faster than me, i was just about to do a PR on that ;) tks |
behat-docs repo has been moved. Just for reference, here is the correct link to the patch https://github.com/Behat/en-docs.behat.org/commit/c1f76bf |
Implements saveScreenshot helper method in MinkContext
Hi,
I just start using behat today, and tried it with the "pt" language. For what i read in doc's i have to change the "en" keywords for the specific language i want to use, but the problem is it throws an exception:
exception
My code:
behat.yml
features/ls.feature
Note: It translates the "passed", "example" and this stuff the only thing doesn't work is the keywords translation
The text was updated successfully, but these errors were encountered: