chore: add npm script to run WebdriverIO test

[fasttime]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[X] Add something to the core
[ ] Other, please explain:

What changes did you make? (Give an overview)

Re-enabled WebdriverIO tests. Added npm script test:wdio to run the WebdriverIO test locally.

Is there anything you'd like reviewers to focus on?

WebdriverIO has been running smoothly in CI for the last couple of months. Shall we try to re-enable it for tests in Jenkins? Or maybe just for local tests?

[netlify]

✅ Deploy Preview for docs-eslint canceled.

Name	Link
🔨 Latest commit	9b57f7e
🔍 Latest deploy log	https://app.netlify.com/sites/docs-eslint/deploys/66074a2c0390a5000842d6be

[aladdin-add]

it was disabled as encountered the error: Command failed: which google-chrome

#17572 (comment)

Is there any way we can verify that it has been fixed?

[fasttime]

it was disabled as encountered the error: Command failed: which google-chrome

#17572 (comment)

Is there any way we can verify that it has been fixed?

Hm, good point. I don't know how this can be verified. But if it's not necessary to run the browser tests in Jenkins maybe we could add a switch to the task in Makefile.js, so the browser test will run locally with npm test?

[mdjermanovic]

I think it's fine not to run the browser test on Jenkins, as we'll always have CI checks right before the release (when @eslnt/js changes are committed).

I also think it's fine to keep the browser test excluded from npm test because it rarely happens that a change breaks these tests and it would eventually be caught in CI anyway. We could add a package.json script that runs the browser test so that if the test happens to fail in CI, the contributor can easily run it locally.

[nzakas]

Yeah, we disabled these on Jenkins because there always seemed to be some configuration issue and we already knew that GitHub CI passed with it running.

I also agree with @mdjermanovic that we don't need to add it to npm test. That command already take a long time to complete, and the browser use case is an edge case that we can watch for during CI.

[fasttime]

I also think it's fine to keep the browser test excluded from npm test because it rarely happens that a change breaks these tests and it would eventually be caught in CI anyway. We could add a package.json script that runs the browser test so that if the test happens to fail in CI, the contributor can easily run it locally.

Thanks! I've re-excluded the browser test from the general test task and added an npm script to run it manually.

[aladdin-add]

wido is just the used tool, and the gha job name is test-on-broswer. :)

Suggested change

	"test:wdio": "node Makefile.js wdio"
	"test:browser": "node Makefile.js wdio"

[fasttime]

Done in 9b57f7e, thanks.

[mdjermanovic]

LGTM, thanks!