Details
-
Suggestion
-
Status: New
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
-
-
20
Description
The current support for multi-language in Cucumber/Gherkin based Tests is incomplete and inconsistent.
What we have:
- there is a global setting that enforces the language whenever exporting feature files. This setting also allows to use the user's profile defined language
- whenever exporting features (by the UI or the REST API), the "Feature" and "Scenario/Scenario Outline" keywords are being translated; the other Gherkin keywords no (e.g. Given, When, And, But, Then)
- the edition of Cucumber Tests/Backgrounds performs syntax highlighting and keywords validation, accordingly with the user profile's defined language
What we could have:
- translate also the Gherkin keywords used in steps (e.g. Given, When, And, But, Then) to the destination language (could this be possible?!)
- ability to choose the export language (as an optional parameter), whenever using the REST API to export/generate cucumber features