as in devtools

Why removing the default values?

I mentioned above, in "proposed changes". Summary: because they have a priority over WDIO_LOG_LEVEL and are obsolete: wdio/logger can handle default value on its own.

Currently if you set WDIO_LOG_LEVEL env variable, you will still see info level logs from devtools and webdriver because devtools.newSession and webdriver.newSession defaulting logLevel to info (devtools and webdriver). Though its not needed because setLogLevelsConfig already sets right logLevels on wdio.remote here, and getLogger already has this fallback with default value.

So it does not affect the behavior if WDIO_LOG_LEVEL is not set, and will use logLevel= process.env.WDIO_LOG_LEVEL if it is.

Let's keep this anyway as it better describes the default behavior. The default log level for @wdio/logger can maybe change in the future and we would like to keep the current default in devtools and webdriver.

Whats about

    options.logLevel = process.env.WDIO_LOG_LEVEL ?? options.logLevel
    const params = validateConfig(DEFAULTS, options)

or

    const params = validateConfig(DEFAULTS, options)
    params.logLevel = process.env.WDIO_LOG_LEVEL?? options.logLevel ?? params.logLevel

in devtools/src/index.ts to set priority as:

1. process.env.WDIO_LOG_LEVEL
2. options.logLevel
3. DEFAULT

Currently DEFAULT priority is higher than process.env.WDIO_LOG_LEVEL, which makes no sense

That works for me 👍

Fixed:

const envLogLevel = process.env.WDIO_LOG_LEVEL as Options.WebDriverLogTypes | undefined
options.logLevel = envLogLevel ?? options.logLevel
const params = validateConfig(DEFAULTS, options)

validateConfig is being called after setting logLevel from process.env so we could verify it