When I run npx nightwatch -e chrome I expect to see my environment name (chrome) logged in the test result in console or "default" if none specified, but when I run my tests in the 3.0.0-beta.1 the environment logs as "undefined"
This will run under 2.6.21, note "chrome" appears on the last line of the test report in console there followed by the suite name and test
npm install nightwatch@3.0.0-beta.1
npm update
npx nightwatch -e chrome
Notice now how that same line shows undefined. Note that if run without an environment default should show there, but in 3.0 even running without an environment specified it will show undefined as well.
Description of the bug/issue
When I run
npx nightwatch -e chrome
I expect to see my environment name (chrome) logged in the test result in console or "default" if none specified, but when I run my tests in the 3.0.0-beta.1 the environment logs as "undefined"Steps to reproduce
This will run under 2.6.21, note "chrome" appears on the last line of the test report in console there followed by the suite name and test
Notice now how that same line shows
undefined
. Note that if run without an environmentdefault
should show there, but in 3.0 even running without an environment specified it will showundefined
as well.Sample test
Command to run
Verbose Output
Nightwatch Configuration
Nightwatch.js Version
3.0.0-beta.1
Node Version
18.16.0
Browser
Chrome 113
Operating System
No response
Additional Information
No response