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 has been archived by the owner on Oct 24, 2021. It is now read-only.
I was thinking of adding capability to the runner to merge configurations from nightwatch.json.
It could work as a merge of two (or more) configuration envs present in nightwatch.json, creating new nightwatch-run.js file that would be passed to nightwatch by using --config ./nightwatch-run.js. Also, it would allow to specify selenium configuration in env, so for instance override webdriver.chrome.driver in chrome-ci env.
Then, in your project using grunt-nightwatchjs, you could specify a task and call it like
grunt seleniumTest:serverEnv+browserEnv
Let me know if I can proceed with implementing this feature request.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I was thinking of adding capability to the runner to merge configurations from nightwatch.json.
It could work as a merge of two (or more) configuration envs present in nightwatch.json, creating new nightwatch-run.js file that would be passed to nightwatch by using
--config ./nightwatch-run.js
. Also, it would allow to specify selenium configuration in env, so for instance override webdriver.chrome.driver in chrome-ci env.Then, in your project using grunt-nightwatchjs, you could specify a task and call it like
Let me know if I can proceed with implementing this feature request.
The text was updated successfully, but these errors were encountered: