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
{{ message }}
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.
I am using cucumber framework with with Protractor 0.23.1.
When there is an error before executing script e.g. Lexing error or undefined object used in step definition or invalid combination capabilities for selenium grid, we won't receive any error message.
We will only get something like this from standard output:
Using the selenium server at http://localhost:4444/wd/hub
[launcher] Running 1 instances of WebDriver[launcher] chrome passed
However, when I execute with 0.20.8 version of protractor, I will receive:
/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:1702
throw error;
^
Error: Lexing error on line 20: 'Click Return to reset the time out and extend your session. You'. See http://wiki.github.com/cucumber/gherkin/lexingerror for more information.
at Lexer.scan (/usr/local/lib/node_modules/cucumber/node_modules/gherkin/lib/gherkin/lexer/en.js:1008:13)
at Object.parse (/usr/local/lib/node_modules/cucumber/lib/cucumber/parser.js:26:25)
at Object.getFeatures (/usr/local/lib/node_modules/cucumber/lib/cucumber/runtime.js:24:35)
at Object.start (/usr/local/lib/node_modules/cucumber/lib/cucumber/runtime.js:10:37)
at Object.runSuiteWithConfiguration (/usr/local/lib/node_modules/cucumber/lib/cucumber/cli.js:19:15)
at Object.run (/usr/local/lib/node_modules/cucumber/lib/cucumber/cli.js:12:14)
at /usr/local/lib/node_modules/protractor/lib/runner.js:178:14
at /usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/base.js:1178:15
at webdriver.promise.ControlFlow.runInNewFrame_ (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:1598:20)
at notify (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:428:12)
==== async task ====
run test preparers
at Runner.runCucumber_ (/usr/local/lib/node_modules/protractor/lib/runner.js:174:35)
at driverprovider_.setupEnv.then.then.then.testResult (/usr/local/lib/node_modules/protractor/lib/runner.js:358:35)
at _fulfilled (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:797:54)
at self.promiseDispatch.done (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:826:30)
at Promise.promise.promiseDispatch (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:759:13)
at /usr/local/lib/node_modules/protractor/node_modules/q/q.js:525:49
at flush (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:108:17)
at process._tickCallback (node.js:415:13)
[launcher] Runner Process Exited With Error Code: 8
It is weird that we are no longer receive anymore error message. It is crucial for debugging.
The text was updated successfully, but these errors were encountered:
I am using cucumber framework with with Protractor 0.23.1.
When there is an error before executing script e.g. Lexing error or undefined object used in step definition or invalid combination capabilities for selenium grid, we won't receive any error message.
We will only get something like this from standard output:
Using the selenium server at http://localhost:4444/wd/hub
[launcher] Running 1 instances of WebDriver[launcher] chrome passed
However, when I execute with 0.20.8 version of protractor, I will receive:
PID: 63441 (capability: chrome #1)
Using the selenium server at http://CDLVDIW700640:5555/wd/hub
/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:1702
throw error;
^
Error: Lexing error on line 20: 'Click Return to reset the time out and extend your session. You'. See http://wiki.github.com/cucumber/gherkin/lexingerror for more information.
at Lexer.scan (/usr/local/lib/node_modules/cucumber/node_modules/gherkin/lib/gherkin/lexer/en.js:1008:13)
at Object.parse (/usr/local/lib/node_modules/cucumber/lib/cucumber/parser.js:26:25)
at Object.getFeatures (/usr/local/lib/node_modules/cucumber/lib/cucumber/runtime.js:24:35)
at Object.start (/usr/local/lib/node_modules/cucumber/lib/cucumber/runtime.js:10:37)
at Object.runSuiteWithConfiguration (/usr/local/lib/node_modules/cucumber/lib/cucumber/cli.js:19:15)
at Object.run (/usr/local/lib/node_modules/cucumber/lib/cucumber/cli.js:12:14)
at /usr/local/lib/node_modules/protractor/lib/runner.js:178:14
at /usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/goog/base.js:1178:15
at webdriver.promise.ControlFlow.runInNewFrame_ (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:1598:20)
at notify (/usr/local/lib/node_modules/protractor/node_modules/selenium-webdriver/lib/webdriver/promise.js:428:12)
==== async task ====
run test preparers
at Runner.runCucumber_ (/usr/local/lib/node_modules/protractor/lib/runner.js:174:35)
at driverprovider_.setupEnv.then.then.then.testResult (/usr/local/lib/node_modules/protractor/lib/runner.js:358:35)
at _fulfilled (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:797:54)
at self.promiseDispatch.done (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:826:30)
at Promise.promise.promiseDispatch (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:759:13)
at /usr/local/lib/node_modules/protractor/node_modules/q/q.js:525:49
at flush (/usr/local/lib/node_modules/protractor/node_modules/q/q.js:108:17)
at process._tickCallback (node.js:415:13)
[launcher] Runner Process Exited With Error Code: 8
It is weird that we are no longer receive anymore error message. It is crucial for debugging.
The text was updated successfully, but these errors were encountered: