Open kathy-ems opened 6 years ago
Looking at the protractor.conf.js
for the generator version you listed (4.1.2), I don't see the lines you said you had to comment out: https://github.com/angular-fullstack/generator-angular-fullstack/blob/fdbb222717cade93a43f403dcb5f5abcb1e32c59/templates/app/protractor.conf.js
Error that is displayed in the console when running
gulp test:e2e
Received an error running
gulp test:e2e
today. Which led me to digging through the selenium-webdriver module, and found that line 95 & 97 ofprotractor.conf
was causing this error. Commenting out these two lines allowsgulp test:e2e
to run.Any idea why? Is this line necessary? I am concerned I will run into problems when testing the browser back button functionality and this cookie/token is missing.
The problem is that getCookie produces an http response LEGACY status code of 14, which is then thrown by the selenium-webdriver.
node_modules/selenium-webdriver/lib/http.js The invalid arguments (command and http response) that is parsed by the function
parseHttpResponse
in node_modules/selenium-webdriver/lib/http.js (line 441) produces the legacy status code of 14.Package.json