Modified globalSetup.ts to make reason and origin of throwBetterErrorMessage more clear

[RossVertizan]

Proposed changes

In working with the WebdriverIO testing, I tried to use the ViTest extension to VSCode and when I ran it I got the error message about having to rename "got". I wasn't really sure where it was coming from and because I had successfully run the tests in a terminal decided that it must being caused by the ViTest plugin or VS Code. Then I realised that the tests would not run in my terminal any more and I got the same error.

The key change is to change "We" to "WebdriverIO", which hopefully makes it clearer where the source of the error is. I have also created a separate message for Setup and TearDown and made them slightly more descriptive of what is happening.

Types of changes

• 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

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 necessary documentation (if appropriate)
• I have added proper type definitions for new commands (if appropriate)

Further comments

Reviewers: @webdriverio/project-committers

[christian-bromann]

The key change is to change "We" to "WebdriverIO", which hopefully makes it clearer where the source of the error is.

👍

I have also created a separate message for Setup and TearDown and made them slightly more descriptive of what is happening.

Can we have it so we have less duplicate text, e.g. using util.format:

const ERROR_MESSAGE = '...%s...'
console.log(util.format(ERROR_MESSAGE, 'teardown')

I hope that illustrates the approach I mean.

[RossVertizan]

Yep, fair enough.

[christian-bromann]

👍

[RossVertizan]

Thank you