Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Step-8 : E2E test got error code: ELIFECYCLE #16739

Closed
2 tasks
sunling opened this issue Oct 19, 2018 · 13 comments
Closed
2 tasks

Step-8 : E2E test got error code: ELIFECYCLE #16739

sunling opened this issue Oct 19, 2018 · 13 comments
Assignees
Milestone

Comments

@sunling
Copy link

sunling commented Oct 19, 2018

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.
selection_015

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 Narretz self-assigned this Oct 25, 2018
@Narretz
Copy link
Contributor

Narretz commented Oct 25, 2018

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

@Narretz Narretz added this to the 1.7.x milestone Oct 25, 2018
@Narretz Narretz assigned gkalpak and unassigned Narretz Oct 25, 2018
@sunling
Copy link
Author

sunling commented Oct 25, 2018

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

  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.
    image

@Narretz
Copy link
Contributor

Narretz commented Oct 25, 2018

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

@sunling
Copy link
Author

sunling commented Oct 25, 2018

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

@gkalpak
Copy link
Member

gkalpak commented Oct 26, 2018

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
Copy link
Author

sunling commented Oct 26, 2018

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

@sunling
Copy link
Author

sunling commented Oct 26, 2018

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

@gkalpak
Copy link
Member

gkalpak commented Oct 26, 2018

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

@sunling
Copy link
Author

sunling commented Oct 26, 2018

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
Copy link
Member

gkalpak commented Oct 26, 2018

🎉 You can safely ignore that warning.

@gkalpak
Copy link
Member

gkalpak commented Oct 26, 2018

BTW, I don't think scenariosbk.js comes from the phonecat repo, does it?

@sunling
Copy link
Author

sunling commented Oct 26, 2018

No. My apologies. It works! What all I need to do is to update protractor.

  1. I re-cloned the phonecat repo
  2. npm install [email protected]
  3. npm run start
  4. npm run protractor

@gkalpak
Copy link
Member

gkalpak commented Oct 26, 2018

Awesome! Glad you got it working.
I'll go ahead and close this issue then (since we are in the process of upgrading our tutorial dependencies as mentioned above).

@gkalpak gkalpak closed this as completed Oct 26, 2018
gkalpak added a commit to gkalpak/angular.js that referenced this issue Nov 2, 2018
Since Protractor requires specific WebDriver versions and these are only
compatible with specific browser version ranges, it is often necessary
to upgrade Protractor just so that it picks up a more recent WebDriver
version.
Related: angular#16739
gkalpak added a commit to gkalpak/angular.js that referenced this issue Nov 2, 2018
Since Protractor requires specific WebDriver versions and these are only
compatible with specific browser version ranges, it is often necessary
to upgrade Protractor just so that it picks up a more recent WebDriver
version.
Related: angular#16739
gkalpak added a commit to gkalpak/angular.js that referenced this issue Nov 5, 2018
Since Protractor requires specific WebDriver versions and these are only
compatible with specific browser version ranges, it is often necessary
to upgrade Protractor just so that it picks up a more recent WebDriver
version.
Related: angular#16739
gkalpak added a commit that referenced this issue Nov 15, 2018
Since Protractor requires specific WebDriver versions and these are only
compatible with specific browser version ranges, it is often necessary
to upgrade Protractor just so that it picks up a more recent WebDriver
version.
Related: #16739

Closes #16753
gkalpak added a commit that referenced this issue Nov 15, 2018
Since Protractor requires specific WebDriver versions and these are only
compatible with specific browser version ranges, it is often necessary
to upgrade Protractor just so that it picks up a more recent WebDriver
version.
Related: #16739

Closes #16753
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants