Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

issue after checkout and start test #2

Closed
spham opened this issue Aug 2, 2019 · 4 comments
Closed

issue after checkout and start test #2

spham opened this issue Aug 2, 2019 · 4 comments

Comments

@spham
Copy link

spham commented Aug 2, 2019

npm run test:cucumber

show issue


> [email protected] test:cucumber /Users/sylvain/intro-to-nightwatchjs
> cucumber-js --require cucumber.conf.js --require step-definitions --format node_modules/cucumber-pretty

Feature: Hacker News Search

  Scenario: Searching Hacker News
    Given I open Hacker News's home page
 Error while running .navigateTo() protocol action: invalid session id

 Error while running .locateMultipleElements() protocol action: invalid session id

 Error while running .locateMultipleElements() protocol action: invalid session id

 Error while running .locateMultipleElements() protocol action: invalid session id

 Error while running .getScreenshot() protocol action: invalid session id

   Creating screenshot was not successful. Response was:
  {
    status: -1,
    state: '',
    value: {
      message: 'invalid session id',
      error: [
        '  (Driver info: chromedriver=2.46.628411 ' +
          '(3324f4c8be9ff2f70a05a30ebc72ffb013e1a71e),platform=Mac OS ' +
          'X 10.12.6 x86_64)'
      ]
    },
    errorStatus: 6,
    error: 'invalid session id',
    httpStatusCode: 200
  }
   {
     status: -1,
     state: '',
     value: {
       message: 'invalid session id',
       error: [
         '  (Driver info: chromedriver=2.46.628411 ' +
           '(3324f4c8be9ff2f70a05a30ebc72ffb013e1a71e),platform=Mac OS ' +
           'X 10.12.6 x86_64)'
       ]
     },
     errorStatus: 6,
     error: 'invalid session id',
     httpStatusCode: 200
   }
       at processTicksAndRejections (internal/process/task_queues.js:89:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] test:cucumber: `cucumber-js --require cucumber.conf.js --require step-definitions --format node_modules/cucumber-pretty`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] test:cucumber script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/sylvain/.npm/_logs/2019-08-02T06_22_22_789Z-debug.log
@spham
Copy link
Author

spham commented Aug 2, 2019

debug show as bellow


0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/usr/local/Cellar/node/12.4.0/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'run',
1 verbose cli   'test:cucumber'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'pretest:cucumber', 'test:cucumber', 'posttest:cucumber' ]
5 info lifecycle [email protected]~pretest:cucumber: [email protected]
6 info lifecycle [email protected]~test:cucumber: [email protected]
7 verbose lifecycle [email protected]~test:cucumber: unsafe-perm in lifecycle true
8 verbose lifecycle [email protected]~test:cucumber: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/sylvain/intro-to-nightwatchjs/node_modules/.bin:/usr/local/opt/[email protected]/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Users/sylvain/anaconda3/bin:/Users/sylvain/anaconda3/condabin:/usr/local/opt/[email protected]/bin:/Applications/Visual Studio Code.app/Contents/Resources/app/bin:/Applications/Visual Studio Code.app/Contents/Resources/app/bin
9 verbose lifecycle [email protected]~test:cucumber: CWD: /Users/sylvain/intro-to-nightwatchjs
10 silly lifecycle [email protected]~test:cucumber: Args: [
10 silly lifecycle   '-c',
10 silly lifecycle   'cucumber-js --require cucumber.conf.js --require ' +
10 silly lifecycle     'step-definitions --format ' +
10 silly lifecycle     'node_modules/cucumber-pretty'
10 silly lifecycle ]
11 silly lifecycle [email protected]~test:cucumber: Returned: code: 1  signal: null
12 info lifecycle [email protected]~test:cucumber: Failed to exec test:cucumber script
13 verbose stack Error: [email protected] test:cucumber: `cucumber-js --require cucumber.conf.js --require step-definitions --format node_modules/cucumber-pretty`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:326:16)
13 verbose stack     at EventEmitter.emit (events.js:200:13)
13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at ChildProcess.emit (events.js:200:13)
13 verbose stack     at maybeClose (internal/child_process.js:1021:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid [email protected]
15 verbose cwd /Users/sylvain/intro-to-nightwatchjs
16 verbose Darwin 16.7.0
17 verbose argv "/usr/local/Cellar/node/12.4.0/bin/node" "/usr/local/bin/npm" "run" "test:cucumber"
18 verbose node v12.4.0
19 verbose npm  v6.10.2
20 error code ELIFECYCLE
21 error errno 1
22 error [email protected] test:cucumber: `cucumber-js --require cucumber.conf.js --require step-definitions --format node_modules/cucumber-pretty`
22 error Exit status 1
23 error Failed at the [email protected] test:cucumber script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]

@aberonni
Copy link
Contributor

aberonni commented Aug 3, 2019

Hi, I suspect this is another example of mucsi96/nightwatch-api#207

I would recommend following up there, in the meantime I will close this issue because I don't think it is related to the code in this repo. Please let me know if you disagree

@aberonni aberonni closed this as completed Aug 3, 2019
@amyng56
Copy link

amyng56 commented Sep 25, 2020

Hi, any update for this issue?

@aberonni
Copy link
Contributor

As I mentioned in my comment above, I don't actually think this is an issue with this repo. However, updating the dependencies might help because I think it has been addressed in an upstream version of nightwatch.

If you would like to submit a PR that updates the version of nightwatch and nightwatch-api then that would be great. Hopefully that will fix this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants