Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Override gherkin keywords #64

Open
picolino opened this issue Mar 12, 2023 · 2 comments
Open

Override gherkin keywords #64

picolino opened this issue Mar 12, 2023 · 2 comments

Comments

@picolino
Copy link

As I see the code, for now we have ability to use english language only to use standard gherkin keywords: Feature, Scenario, Given, When, Then

Seems like it will be good feature if end users will be able to override these keywords, for example, if we need to create gherkin tests on the other language.

@mchaloupka
Copy link
Collaborator

Hi,

this is an interesting idea. It may not be so hard to do it, but I am wondering whether it really has a use case. Gherking language seems to be defined and can be considered almost as a programming language with defined keywords which everyone seems to understand (as soon as you know what Gherkin is).

I remember Excel allowing localized macros and they did not work in Excel instances without the particular language support. So, in the end it was a terrible feature. I would love to avoid that here.

Can you please clarify what kind of users would benefit from this? Or, are there any Gherkin frameworks supporting that?

@picolino
Copy link
Author

Official cucumber documentation provides specification for different languages:

https://cucumber.io/docs/gherkin/languages/

So I think it will be useful out of the box. Also, Domain context from gherkin tests is easy to understand if they wrote on the same language business speak.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

2 participants