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
We would like to use this plugin for our test integration with Testlink. And since we are working in a strictly German speaking environment all our feature file use german keywords, e. g.:
Feature = Funktionalität
Scenario = Szenario
Given = Gegeben sei
Would it be possible for this plugin to support all the keywords, that cucumber itself is supporting?
Would be really great.
I supplied a code suggestion. Usage of the element type instead of the element keyword will avoid the restriction to one cucumber dialect. Type scenario and/or background will be the same in all dialects. The corresponding keywords will not.
…p to master
* commit '73802211c0aa8454199bd08cf14e3dc66e2079e6':
Changelog : - code refactoring - code clean up - apply same logic for all supported reports : cucumber, jbehave, earlgrey
- capability to group all scenario per test suite id
- performance optimization - add test case
changelog : - code refactor
Changelog : - code refactoring - performance improvement attempt
We would like to use this plugin for our test integration with Testlink. And since we are working in a strictly German speaking environment all our feature file use german keywords, e. g.:
Would it be possible for this plugin to support all the keywords, that cucumber itself is supporting?
Would be really great.
I supplied a code suggestion. Usage of the element type instead of the element keyword will avoid the restriction to one cucumber dialect. Type scenario and/or background will be the same in all dialects. The corresponding keywords will not.
TestResultReader.txt
The text was updated successfully, but these errors were encountered: