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

Running Chimp in cucumber mode on windows produces an error #432

Closed
kwright1 opened this issue Jul 27, 2016 · 19 comments
Closed

Running Chimp in cucumber mode on windows produces an error #432

kwright1 opened this issue Jul 27, 2016 · 19 comments
Assignees

Comments

@kwright1
Copy link

Expected behaviour

Chimp starts up without issue.

I think this might be a re-manifestation of an old problem where some cucumber stuff was splitting on ':' for absolute paths

Actual behaviour

module.js:442
throw err;
^

Error: Cannot find module 'C'
at Function.Module._resolveFilename (module.js:440:15)
at Function.Module._load (module.js:388:25)
at Module.require (module.js:468:17)
at require (internal/module.js:20:19)
at Array.forEach (native)
at Object.initializer (C:\Users\Kyle\webdriverio-test\node_modules\cucumber\lib\cucumber\cli\support_code_loader.js:22:25)
at Object.Library (C:\Users\Kyle\webdriverio-test\node_modules\cucumber\lib\cucumber\support_code\library.js:120:25)
at Object.getSupportCodeLibrary (C:\Users\Kyle\webdriverio-test\node_modules\cucumber\lib\cucumber\cli\support_code_loader.js:10:58)
at Object.getSupportCodeLibrary (C:\Users\Kyle\webdriverio-test\node_modules\cucumber\lib\cucumber\cli\configuration.js:126:32)
at Object.getSupportCodeLibrary (C:\Users\Kyle\webdriverio-test\node_modules\cucumber\lib\cucumber\runtime.js:43:46)

Steps to reproduce the problem

I just did a fresh install of node + chimp and tried to run chimp --watch

Used version
  • Chimp: 0.39.0
  • Node.js: 6.3.1
  • Operation system: Windows
Console / Log Output

$ ./node_modules/.bin/chimp --watch
[chimp] Watching features with tagged with @Focus,@dev,@watch

[chimp] Running...
module.js:442
throw err;
^

Error: Cannot find module 'C'
at Function.Module._resolveFilename (module.js:440:15)
at Function.Module._load (module.js:388:25)
at Module.require (module.js:468:17)
at require (internal/module.js:20:19)
at Array.forEach (native)
at Object.initializer (C:\Users\Kyle\webdriverio-test\node_modules\cucumber\lib\cucumber\cli\support_code_loader.js:22:25)
at Object.Library (C:\Users\Kyle\webdriverio-test\node_modules\cucumber\lib\cucumber\support_code\library.js:120:25)
at Object.getSupportCodeLibrary (C:\Users\Kyle\webdriverio-test\node_modules\cucumber\lib\cucumber\cli\support_code_loader.js:10:58)
at Object.getSupportCodeLibrary (C:\Users\Kyle\webdriverio-test\node_modules\cucumber\lib\cucumber\cli\configuration.js:126:32)
at Object.getSupportCodeLibrary (C:\Users\Kyle\webdriverio-test\node_modules\cucumber\lib\cucumber\runtime.js:43:46)


Join our Slack xolv.io/community #chimp channel, where you can find help and help others.

@GeeChao
Copy link

GeeChao commented Aug 8, 2016

Also getting the same error on my end on Windows. Is there currently a workaround fix for this issue?

@GeeChao
Copy link

GeeChao commented Aug 16, 2016

Have tried version 0.34 as suggested by @samhatoum and is currently working on Windows wth version 4.4.7 of NodeJS

@MacDennis76
Copy link

Any idea when this issue will be fixed? Tried the latest version, does not work on Windows 10. Reverting to 0.34 does work.

@samhatoum
Copy link
Member

@MacDennis76 which version of node? Have you tried with Node 6.5.0?

@mmcculloch15
Copy link

On Windows 7 I'm getting the same error if I update to any version of chimp past 0.38, and any version of node past 5.12.0.

@cloughney
Copy link

Same issue here, encountered on multiple machines with Windows 10. Have tried on node v5.11.0 and v6.5.0 with the latest version of chimp. Everything works correctly with chimp v0.34.

@pkoppula15
Copy link

I am having the same Issue. Any idea when this would be fixed ? Works fine with 0.34 but I am missing new features of the latest version.

@ghost
Copy link

ghost commented Sep 20, 2016

This could be the absolute path that we pass to cucumber for the JavaScript transpilation.

compiler: 'js:' + path.resolve(__dirname, '../lib/babel-register.js'),

@samhatoum
Copy link
Member

samhatoum commented Sep 20, 2016

you can test this by overriding the compiler option in a config file, or by passing chimp --compiler=<path to babel-register.js>

@tychedelia
Copy link

Specifying the absolute path in my custom configuration doesn't help. I'm successfully able to require babel-register.js using the path returned by path.resolve in the Node REPL, but it still chokes when passed to to cucumber. It looks like cucumber/cli is just mapping require onto the path, so I assume the path is getting mangled somewhere in cucumber. Going to investigate a little more and report back.

@samhatoum
Copy link
Member

awesome, thank you @james-mcelwain

@ghost
Copy link

ghost commented Sep 20, 2016

Here is the fix: TheBrainFamily/cucumber-js@7fdbc5c. For some reason it is not in the current release anymore.

@tychedelia
Copy link

@sanjo Awesome! Any chance you could get this merged to close this? We're trying to get a proof of concept for some automated testing stuff using Chimp and this has been a big annoyance for us. Thanks!

@samhatoum samhatoum assigned samhatoum and unassigned lgandecki Sep 21, 2016
@pkoppula15
Copy link

Any update on the new build with the fix ?

samhatoum added a commit to TheBrainFamily/cucumber-js that referenced this issue Sep 22, 2016
@samhatoum
Copy link
Member

Fixed in 0.41.0

@samhatoum
Copy link
Member

@pkoppula15 and @james-mcelwain please let me know if this works for you

@pkoppula15
Copy link

Thanks @samhatoum , I'll give a shot and let you know.

@pkoppula15
Copy link

pkoppula15 commented Sep 22, 2016

It works now. Thanks @samhatoum .
Node Version : 6.6.0
Chimp Version : 0.41.0

@MacDennis76
Copy link

MacDennis76 commented Sep 22, 2016

Yes, confirmed working with node 4.5.0. Node 6.6.0 does not work with Chimp on my workstation but it's my guess that the reason is selenium standalone and their NodeJS support policy.

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

9 participants