How to fix error: Could not find update-config.json. Run ‘webdriver-manager update’ to download binaries.
Sometimes while running your Protractor test you get the error ‘Could not find update-config.json’ and in most cases when updating webdriver manager you get this error.
[17:05:22] I/launcher – Running 1 instances of WebDriver [17:05:22] I/direct – Using ChromeDriver directly… [17:05:22] E/direct – Error code: 135 [17:05:22] E/direct – Error message: Could not find update-config.json. Run ‘webdriver-manager update’ to download binaries. [17:05:22] E/direct – Error: Could not find update-config.json. Run ‘webdriver-manager update’ to download binaries. at Direct.getNewDriver (C:automationDemoprotractor-jasmine-typescriptnode_modulesprotractorbuiltdriverProvidersdirect.js:63:31) at Runner.createBrowser (C:automationDemoprotractor-jasmine-typescriptnode_modulesprotractorbuiltrunner.js:195:43) at q.then.then (C:automationDemoprotractor-jasmine-typescriptnode_modulesprotractorbuiltrunner.js:339:29) at _fulfilled (C:automationDemoprotractor-jasmine-typescriptnode_modulesqq.js:834:54) at self.promiseDispatch.done (C:automationDemoprotractor-jasmine-typescriptnode_modulesqq.js:863:30) at Promise.promise.promiseDispatch (C:automationDemoprotractor-jasmine-typescriptnode_modulesqq.js:796:13) at C:automationDemoprotractor-jasmine-typescriptnode_modulesqq.js:556:49 at runSingle (C:automationDemoprotractor-jasmine-typescriptnode_modulesqq.js:137:13) at flush (C:automationDemoprotractor-jasmine-typescriptnode_modulesqq.js:125:13) at _combinedTickCallback (internal/process/next_tick.js:131:7) [17:05:22] E/launcher – Process exited with error code 135 npm ERR! Test failed. See above for more details. PS C:automationDemoprotractor-jasmine-typescript>
Answer:
- Open Command prompt or terminal.
- Go to your project root directory.
- Enter the below command and hit Enter key.
node node_modules/protractor/bin/webdriver-manager update
This command will update the WebDriver Manager.
Run your test again.
You are Done!!!
