You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At my company we are using specifications written in the german Gherkin dialect. However, Testomatio only understands the english Gherkin dialect. In consequence, we cannot use some of Testomatio's features. For example, no steps show up in the "Steps" tab.
Since we thought that the steps shown in the "Steps" tab are the scenarioJson.steps extracted by the getSourceCode function of this tool, we implemented a translation mechanism in the keyword-translation branch of our fork. Unfortunately, this approach does not work: the Testomatio backend seems to ignore the steps array sent by this tool regardless of the language of the keyword fields.
If you can confirm that scenarioJson.steps is obsolete, I can submit a PR for its removal.
The text was updated successfully, but these errors were encountered:
At my company we are using specifications written in the german Gherkin dialect. However, Testomatio only understands the english Gherkin dialect. In consequence, we cannot use some of Testomatio's features. For example, no steps show up in the "Steps" tab.
Since we thought that the steps shown in the "Steps" tab are the
scenarioJson.steps
extracted by thegetSourceCode
function of this tool, we implemented a translation mechanism in thekeyword-translation
branch of our fork. Unfortunately, this approach does not work: the Testomatio backend seems to ignore thesteps
array sent by this tool regardless of the language of thekeyword
fields.If you can confirm that
scenarioJson.steps
is obsolete, I can submit a PR for its removal.The text was updated successfully, but these errors were encountered: