(wdio-config): add outputDir default

[erwinheitzman]

Proposed changes

By default all the webdriver logs are put into the browser. This PR changes this so that the logs are now stored at {wdio root}/.wdio-artifacts/logs, making for a smoother experience and less confusion when people see errors that are not important to them (test passes but there is a webdriver error).

Marked as a breaking change because people could be relying on the logs in some ways that we cannot anticipate.

Types of changes

• Polish (an improvement for an existing feature)
• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (improvements to the project's docs)
• Specification changes (updates to WebDriver command specifications)
• Internal updates (everything related to internal scripts, governance documentation and CI files)

Checklist

• I have read the CONTRIBUTING doc
• I have added tests that prove my fix is effective or that my feature works
• I have added the necessary documentation (if appropriate)
• I have added proper type definitions for new commands (if appropriate)

Reviewers: @webdriverio/project-committers

[christian-bromann]

wdyt?

[christian-bromann]

I wonder if we should call the directory just wdio and maybe start recommending using this for all WebdriverIO related files, e.g. logs, baselines and config files

[erwinheitzman]

I like this idea a lot and am thinking about a .wdio directory so that it is clear that this contains configuration files and more.
It also means the files are at the top in your IDE which is useful as you have all you configuration related files in one location (any dot files (directories) will all live at the top). What do you think? 🙂

[christian-bromann]

This makes sense to me. I would have one request which would be to allow users to store wdio logs to stdout and in stdout at the same time. AFAIK right now users can only decide between either of them and I think it makes sense to allow the scenario to make both possible.

Background: I personally like to have these WebDriver commands prinited in stdout so I can immediately debug them as my test go on and I print stuff in the console. If we set a default outputDir I would need to comment in/out the output dir option.

I think I would be fine if I can disable the outputDir option by just passing in a --no-outputDir but not sure if yargs supports recognises this and overwrites the hard coded property in the config with undefined. Alternatively I can imagine to pass in a --stdout-logging or just --stdout to enable both.