✅ Deploy Preview for docs-eslint canceled.

Thanks for the new pull request @Pixel998. I can see that the browser test is still running quite slowly in CI. The current run took over 8 minutes. I was trying to use cypress-io/github-action to speed it up, but it didn't help. So I'm not sure. Either Cypress is just this lame in GitHub or we don't know how to set it up properly.

Maybe we could try https://modern-web.dev/docs/test-runner/overview/ instead.

@fasttime So it appears that making Cypress not render the runner ui fixes the performance issue.

I think this is quite acceptable now. It's not as fast as WebdriverIO but still faster then Mocha unit tests and it never timed out in my test runs. Probably it isn't even necessary to use Firefox as a browser.

Note that the output of the Test step is showing two strange warnings:

Couldn't find tsconfig.json. tsconfig-paths will be skipped

tput: No value for $TERM and no -T specified

The first warning is filed as a bug in Cypress (cypress-io/cypress#21805 and cypress-io/cypress#22273), so maybe we could leave it as it is until they fix it. If we want to get rid of the warning, we could create a directory cypress with a TS config file cypress/tsconfig.json in it, move cypress.config.js to cypress/config.js and launch Cypress with the CLI option --config-file=cypress/config.js. That would remove the warning without adding an unnecessary tsconfig.json file at the repo root.

The second warning seems to only occur when --no-runner-ui is specified. It can be fixed by defining a TERM environment variable in .github/workflows/ci.yml:

  test_on_browser:
    name: Browser Test
    runs-on: ubuntu-latest
+   env:
+     TERM: xterm-256color

Clearly there are also other options.

Probably it isn't even necessary to use Firefox as a browser.

You're right. Chrome is now as fast locally, so I've switched back to it.

The first warning is filed as a bug in Cypress ...

I think we can avoid the workaround for now. Given that the warning isn't causing any major issues, waiting for the Cypress fix seems like the best approach. Unless you have a strong preference for implementing the workaround, I'd suggest we leave it as is.

The second warning seems to only occur when --no-runner-ui is specified. It can be fixed by defining a TERM environment variable in .github/workflows/ci.yml:

Done.

I think the output of Cypress is also easier to read. For comparison, this is what a test failure in GitHub Actions currently looks like with WebdriverIO — notice that there's no stack trace:

And this is the same failure with Cypress and the progress reporter, the same one we use for Mocha unit tests: