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
Current situation:
Currently protractor-flake for CucumberJS can use 2 parsers, the cucumber.js and the cucumber.multi.js parser. The first parser is based on the logging of the framework for CucumberJS < 0.9.0 and the second one is based on a console.log.
Desired situation:
Replace both parsers with a new parser that will read the log based on a console.log users need to add to their framework. This is currently already advised for CucumberJS 1.
The advantage of parsing the log of protractor based on a console.log is that it will be more stable and framework independent then the current parsing because that one is based on the logging of the framework itself.
To do:
[] create a new parser called cucumber, the other ones will be removed and this will result in a new major release
[] test this for CucumberJS 1, 2 and 3
[] create new unit tests
[] create new docs for cucumber with examples how to implement this for CucumberJS 1, 2 and 3
The text was updated successfully, but these errors were encountered:
This change simplifies the cucumber parsers and brings them down to 1 parser.
The docs are also updated with usage examples.
ClosesNickTomlin#71
BREAKING CHANGE: cucumberMulti parser can't be used anymore
To migrate change `cucumberMulti` to `cucumber`
Current situation:
Currently protractor-flake for CucumberJS can use 2 parsers, the cucumber.js and the cucumber.multi.js parser. The first parser is based on the logging of the framework for CucumberJS < 0.9.0 and the second one is based on a
console.log
.Desired situation:
Replace both parsers with a new parser that will read the log based on a
console.log
users need to add to their framework. This is currently already advised for CucumberJS 1.The advantage of parsing the log of protractor based on a
console.log
is that it will be more stable and framework independent then the current parsing because that one is based on the logging of the framework itself.To do:
cucumber
, the other ones will be removed and this will result in a new major releaseThe text was updated successfully, but these errors were encountered: