Open picolino opened 1 year ago
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?
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.
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.