This is fixed with latest release of selenium webdriver: selenium-server-standalone-3.14.0.jar. I can now launch a suite of Nightwatch tests and proxy through ZAP.
{
"src_folders" : ["tests"],
"output_folder" : "reports",
"custom_commands_path" : "./lib/customCommands",
"custom_assertions_path" : "./lib/customAssertions",
"page_objects_path" : ["pages", "pages/myApp"],
"globals_path" : "",
"selenium" : {
"start_process" : true,
"server_path" : "./lib/drivers/selenium/selenium-server-standalone-3.14.0.jar",
"log_path" : "logs",
"port" : 4444,
"cli_args" : {
"webdriver.chrome.driver" : "./lib/drivers/chromedriver_2_41/chromedriver.exe",
"webdriver.gecko.driver" : "./lib/drivers/geckodriver-v0.21.0-win64/geckodriver.exe",
"webdriver.edge.driver" : "./lib/drivers/Edge16299/MicrosoftWebDriver.exe",
"webdriver.ie.driver": "./lib/drivers/IEDriverServer_x64_3.13.0/IEDriverServer.exe",
"ie.setProxyByServer":true
}
},
"test_settings" : {
"default" : {