WebStorm won't run protractor

I'm trying to start doing API integration tests using protractor. I have setup my spec file with a test and I have my own config. If I run the test from a command prompt, everything works fine. If I try to setup WebStorm to run the tests I always get:

"C:\Program Files\nodejs\node.exe" C:\source\myProject\node_modules\protractor\bin\protractor "C:\Program Files\JetBrains\WebStorm 2019.2.1\plugins\JavaScriptLanguage\helpers\protractor-intellij\lib\protractor-intellij-config.js" --intellijOriginalConfigFile=C:\source\myProject\e2e\integration.conf.js --disableChecks
[07:12:46] I/launcher - Running 1 instances of WebDriver
[07:12:46] I/direct - Using ChromeDriver directly...
[07:12:46] E/direct - Error code: 135
[07:12:46] E/direct - Error message: Could not find update-config.json. Run 'webdriver-manager update' to download binaries.
[07:12:46] E/direct - Error: Could not find update-config.json. Run 'webdriver-manager update' to download binaries.
at Direct.getNewDriver (C:\source\myProject\node_modules\protractor\built\driverProviders\direct.js:63:31)
at Runner.createBrowser (C:\source\myProject\node_modules\protractor\built\runner.js:195:43)
at C:\source\myProject\node_modules\protractor\built\runner.js:339:29
at _fulfilled (C:\source\myProject\node_modules\q\q.js:834:54)
at C:\source\myProject\node_modules\q\q.js:863:30
at Promise.promise.promiseDispatch (C:\source\myProject\node_modules\q\q.js:796:13)
at C:\source\myProject\node_modules\q\q.js:556:49
at runSingle (C:\source\myProject\node_modules\q\q.js:137:13)
at flush (C:\source\myProject\node_modules\q\q.js:125:13)
at processTicksAndRejections (internal/process/task_queues.js:79:11)
[07:12:46] E/launcher - Process exited with error code 135

Process finished with exit code 135

 

my configuration:

 

However, if I run the protractor integration.conf.js from a command prompt, it executes just fine.  Any idea on what's wrong?

 

Thanks

 

3 comments
Comment actions Permalink

>if I run the protractor integration.conf.js from a command prompt, it executes just fine.

what directory do you run this command in? Is it a project root folder, e2e folder, or?

Does running node node_modules/protractor/bin/webdriver-manager update in the root folder fix the issue?

0
Comment actions Permalink

Running the update did nothing.

So i did find the problem.  I choose the option to install globally.  in my testing i must of tried installing locally a well, but webStorm would only see the local install.  It wouldn't notice the global install until i tried creating a new conf file from the protractor template option, then it would see the global option.

 

Now if i can just figure out why wants to make a new config file based on my test file's describe statement....  two steps forward, one step back.

0
Comment actions Permalink

>webStorm would only see the local install.  

it suggest a local package by default, but you can choose the global protractor instead in the Protractor package: field

 

>Now if i can just figure out why wants to make a new config file based on my test file's describe statement.... 

 

haven't got what you mean... Please could you elaborate on this?

0

Please sign in to leave a comment.