You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 29, 2024. It is now read-only.
It appears that arguments used when running protractor from the command line do not override values in the conf.js file. For example, if I run the command
protractor --baseUrl='http://local.app' conf.js
with the conf.js file
module.export={// some other paramscapabilities: {'browserName': (process.env.TEST_BROWSER_NAME||'chrome'),'version': (process.env.TEST_BROWSER_VERSION||'ANY')},baseUrl: 'http://test.app'}
tests will execute using the baseUrl = 'http://test.app' in the conf.js instead of 'http://local.app'.
It could be that this is a specific issue to my setup, but it'd be helpful to allow the CLI to override parameters as needed in the conf.js file.
It appears that arguments used when running protractor from the command line do not override values in the conf.js file. For example, if I run the command
with the conf.js file
tests will execute using the baseUrl = 'http://test.app' in the conf.js instead of 'http://local.app'.
It could be that this is a specific issue to my setup, but it'd be helpful to allow the CLI to override parameters as needed in the conf.js file.