Closed ruisalgado closed 6 years ago
Setting any valid arg will have nightwatch overwrite the default settings as expected. So while the []
bug persists, I'd suggest just setting some (seemingly innocuous) args from the available list. Say... --default
looks like a good candidate.
Is there a Nightwatch issue for this we can track?
See nightwatchjs/nightwatch#1729.
stacktrace: 'org.openqa.selenium.WebDriverException: unknown error: cannot parse capability: chromeOptions\nfrom unknown error: cannot parse args\nfrom unknown error: must be a list\n
This happens because in the
nonHeadless
nightwatch test env, we set chromeOptions args to null.Setting the args to
[]
doesn't work unfortunately, as there's a bug in nightwatch that will cause the default settings to be used, thus reintroducing--headless
.