Feature and motivation
Currently, Java logs Executing: and Executed: , but when and exception is thrown, the output is a duplication of the Executing: command, rather than what the actual error is. Error should be getting logged.
Usage example
Should look like this:
2023-02-12 13:22:39 FINE - Exception: org.openqa.selenium.SessionNotCreatedException: Could not start a new session. Response code 400. Message: httpProxy is not a valid URL: user:password@host:port
Host info: host: 'SL-1495.attlocal.net', ip: '192.168.1.66'
Build info: version: '4.8.0', revision: '267030adea'
System info: os.name: 'Mac OS X', os.arch: 'x86_64', os.version: '10.16', java.version: '11.0.6'
Driver info: driver.version: FirefoxDriver
instead of:
2023-02-12 13:22:39 FINE - Exception: [null, newSession {capabilities=[Capabilities {acceptInsecureCerts: true, browserName: firefox, moz:debuggerAddress: true, moz:firefoxOptions: {}, proxy: Proxy(manual, http=user:pas...}], desiredCapabilities=Capabilities {acceptInsecureCerts: true, browserName: firefox, moz:debuggerAddress: true, moz:firefoxOptions: {}, proxy: Proxy(manual, http=user:pas...}}]
Feature and motivation
Currently, Java logs
Executing:andExecuted:, but when and exception is thrown, the output is a duplication of theExecuting:command, rather than what the actual error is. Error should be getting logged.Usage example
Should look like this:
instead of: