Step-8 : E2E test got error code: ELIFECYCLE

[sunling]

I'm submitting a ...

• [ x] bug report
• feature request
• other

Current behavior:

Followed up Step- 8 - Templating Links & Images, when I tried to run 'npm run protractor' this command. Browser opened with url http://localhost:8000/index.html but couldn't open the index page
When I checked the log , I got error code ELIFECYCLE.

Expected / new behavior:

E2E test should run properly

Minimal reproduction of the problem with instructions:

AngularJS version: 1.7.x-snapshot

Browser: [all | Chrome XX | Firefox XX | Edge XX | IE XX | Safari XX | Mobile Chrome XX | Android X.X Web Browser | iOS XX Safari | iOS XX UIWebView | iOS XX WKWebView ]

Chrome Version 70.0.3538.67 (Official Build) (64-bit)

Anything else:

Is something wrong with protractor. should we install protractor first? (tried, failed,same error)
In this tutorial, it didn't mention about installing protractor. if we need to , what's the version ?

[Narretz]

It looks like we need to update protractor, which will then update the Chromedriver.
In the mean time you can do npm install protractor@5.4.1 and then re-run, which should install the latest Chromedriver.

[sunling]

I updated protractor to 5.4.1 and installed the latest chromedriver. package.json look like this.

1. run npm run start command first

2. Open a new terminal window, run npm run protractor. it worked. But the test failed because i guess the logic is not right.
   

[Narretz]

The tests work for me (in Windows). Did you change something in the code?

[sunling]

No. I reset the workspace to step 8 by running git checkout -f step-8. I am using Linux(to be specifc gLinux).

[gkalpak]

I am in the process of upgrading the tutorial (on last time 😢) to v1.7.x. I will ensure the tests pass with the upgraded deps.
In the mean time, can you try running the tests a few times and see if you get the exact same failures consistently?

[sunling]

I tested for 3 times , same as the first time(the screenshot showed at previous comment).

[sunling]

Why there is a scenariosbk.js file ? It seems it is not the same as scenarios.js file.

[gkalpak]

No idea where the *bk.js file came from 😁

[sunling]

I changed a little bit on the scenariosbk.js . Two of tests passed. There is only a warning left which says browser.getLocationAbsUrl() is deprecated

[gkalpak]

🎉 You can safely ignore that warning.