Transcavator in STS IDE & # 8594; Failed to find update-config.json

Question

I currently have Protractor v.5.1.1, Node.js v.6.10.0

All weighting tests work in the window console, but when I try to run them from the STS IDE, I get below the error. Of course, I did an update to webdriver-manager, but that doesn't help at all. Does anyone know how to solve this problem?

Below errors, respectively, when I use or not 'directConnect'

[22:21:48] I/launcher - Running 1 instances of WebDriver [22:21:48] I/direct - Using ChromeDriver directly... [22:21:48] E/direct - Error code: 135 [22:21:48] E/direct - Error message: Could not find update-config.json. Run 'webdriver-manager update' to download binaries. [22:21:48] E/direct - Error: Could not find update-config.json. Run 'webdriver-manager update' to download binaries. at IError (D:\STS_workspace\jgh\node_modules\protractor\built\exitCodes.js:5:1) at ProtractorError (D:\STS_workspace\jgh\node_modules\protractor\built\exitCodes.js:10:9) at BrowserError (D:\STS_workspace\jgh\node_modules\protractor\built\exitCodes.js:51:9) at Direct.getNewDriver (D:\STS_workspace\jgh\node_modules\protractor\built\driverProviders\direct.js:62:31) at Runner.createBrowser (D:\STS_workspace\jgh\node_modules\protractor\built\runner.js:194:43) at q.then.then (D:\STS_workspace\jgh\node_modules\protractor\built\runner.js:338:29) at _fulfilled (D:\STS_workspace\jgh\node_modules\q\q.js:834:54) at self.promiseDispatch.done (D:\STS_workspace\jgh\node_modules\q\q.js:863:30) at Promise.promise.promiseDispatch (D:\STS_workspace\jgh\node_modules\q\q.js:796:13) at D:\STS_workspace\jgh\node_modules\q\q.js:556:49 [22:21:48] E/launcher - Process exited with error code 135 

or

 [21:19:23] I/launcher - Running 1 instances of WebDriver [21:19:23] E/local - Error code: 135 [21:19:23] E/local - Error message: No update-config.json found. Run 'webdriver-manager update' to download binaries. [21:19:23] E/local - Error: No update-config.json found. Run 'webdriver- manager update' to download binaries. at IError (D:\STS_workspace\jgh\node_modules\protractor\built\exitCodes.js:5:1) at ProtractorError (D:\STS_workspace\jgh\node_modules\protractor\built\exitCodes.js:10:9) at BrowserError (D:\STS_workspace\jgh\node_modules\protractor\built\exitCodes.js:51:9) at Local.addDefaultBinaryLocs_ (D:\STS_workspace\jgh\node_modules\protractor\built\driverProviders\local.js:40:23) at Local.setupDriverEnv (D:\STS_workspace\jgh\node_modules\protractor\built\driverProviders\local.js:81:14) at Local.setupEnv (D:\STS_workspace\jgh\node_modules\protractor\built\driverProviders\driverProvider.js:110:34) at q.then (D:\STS_workspace\jgh\node_modules\protractor\built\runner.js:334:41) at _fulfilled (D:\STS_workspace\jgh\node_modules\q\q.js:834:54) at self.promiseDispatch.done (D:\STS_workspace\jgh\node_modules\q\q.js:863:30) at Promise.promise.promiseDispatch (D:\STS_workspace\jgh\node_modules\q\q.js:796:13) [21:19:23] E/launcher - Process exited with error code 135 

My conf.js looks like this:

 var SpecReporter = require('jasmine-spec-reporter').SpecReporter; exports.config = { // directConnect:true, specs: ['spec4.js'], framework: 'jasmine2' , onPrepare: function () { jasmine.getEnv().addReporter(new SpecReporter({ spec: { displayStacktrace: true, displaySuccessesSummary: true, displayFailuresSummary: true, displayPendingSummary: true, displaySpecDuration: true, }, })); }, jasmineNodeOpts: { defaultTimeoutInterval: 25000, print: function () {}, }, 

I do not have a selenium folder in the path node_modules / protractor / node_modules / webdriver-manager, but I have package.json where I added "webdriver-update": "Updating webdriver-manager". This is the output of npm run webdriver-update:

  D:\STS_workspace\jgh>npm run webdriver-update npm WARN invalid config proxy="http:" npm WARN invalid config Must be a full url with 'http://' npm WARN invalid config proxy="http:" npm WARN invalid config Must be a full url with 'http://' npm ERR! Windows_NT 10.0.14393 npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "webdriver-update" npm ERR! node v6.10.0 npm ERR! npm v3.10.10 npm ERR! path D:\STS_workspace\jgh\package.json npm ERR! code ENOENT npm ERR! errno -4058 npm ERR! syscall open npm ERR! enoent ENOENT: no such file or directory, open 'D:\STS_workspace\jgh\package.json' npm ERR! enoent ENOENT: no such file or directory, open 'D:\STS_workspace\jgh\package.json' npm ERR! enoent This is most likely not a problem with npm itself npm ERR! enoent and is related to npm not being able to find a file. npm ERR! enoent npm ERR! Please include the following file with any support request: npm ERR! D:\STS_workspace\jgh\npm-debug.log 

Answer 1

It looks like you are either using directConnect or starting with the local driver provider (without seleniumAddress or directConnect ) in your configuration file. You need to run webdriver-manager update .

I used to have extra flags to not download standalone or gecko with webdriver-manager update --standalone false --gecko false . This is no longer the case if you start with a local driver provider. You will need a separate jar selenium file.

You can run this using the script in package.json. Something like:

 "scripts": { "webdriver-update": "webdriver-manager update" } 

Then do the following: npm run webdriver-update . How do you check if binaries exist? In your project go to node_modules/protractor/node_modules/webdriver-manager/selenium/ . Here are update-config.json and downloaded executables.

Answer 2

You can try updating it this way, it will definitely update it in node_modules / protractor:

 $ ./node_modules/protractor/bin/webdriver-manager update 

Answer 3

Just run webdriver-manager with the npx command in the project folder;

 npx webdriver-manager update 

Answer 4

On MacOS, I resolved this error by adding seleniumAddress to my Protractor configuration file (I used directConnect before, so commented on this):

 // directConnect: true, // baseUrl: 'http://localhost:4000/', seleniumAddress: 'http://localhost:4444/wd/hub/', 

Now I start the Protractor server by running: $ webdriver-manager start

And in another terminal window, I run tests with: $ ng e2e

Answer 5

You just need to run this command and it will fix it - npm run webdriver-update updates your web driver in the node_modules section under node_modules/protractor .

These 2 lines are the main culprits. Just try this command and it should solve your problem.

 [22:21:48] E/direct - Error message: Could not find update-config.json. Run 'webdriver-manager update' to download binaries. [22:21:48] E/direct - Error: Could not find update-config.json. Run 'webdriver-manager update' to download binaries. 

Hope this helps!