New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Running tests from serenity-js-cucumber-webdriverio template on Windows gives ERR_UNSUPPORTED_ESM_URL_SCHEME error #2060
Labels
Comments
jan-molak
added a commit
to serenity-js/serenity-js-cucumber-template
that referenced
this issue
Nov 11, 2023
jan-molak
added a commit
to serenity-js/serenity-js-cucumber-template
that referenced
this issue
Nov 11, 2023
Demonstrate support for Windows (serenity-js/serenity-js#2060)
jan-molak
added a commit
to serenity-js/serenity-js-cucumber-playwright-template
that referenced
this issue
Nov 11, 2023
jan-molak
added a commit
to serenity-js/serenity-js-cucumber-playwright-template
that referenced
this issue
Nov 11, 2023
Demonstrate support for Windows - serenity-js/serenity-js#2060
OK, so it looks like it's just the WebdriverIO integration that seems to be affected by this issue (see serenity-js/serenity-js-cucumber-webdriverio-template#559). Playwright and plain Cucumber integrations seem fine. I'll have a look into what could be causing it for WebdriverIO. |
jan-molak
added a commit
that referenced
this issue
Nov 11, 2023
…ng error Cucumber fomatter path must now be quoted, as per the docs - https://github.com/cucumber/cucumber-js/blob/main/docs/deprecations.md#ambiguous-colons-in-formats Related tickets: #2060
jan-molak
added a commit
that referenced
this issue
Nov 14, 2023
use the same mechanisms for resolving paths to specs and "requires" to ensure consistency Related tickets: #2060
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
When I try to run the tests from the above template I get the following error: ERROR @wdio/runner: Error [ERR_UNSUPPORTED_ESM_URL_SCHEME]: Only URLs with a scheme in: file, data, and node are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
What did you expect to happen?
Tests would run without error
Node.js version
18.17.1
Execution environment
Windows 11/Chrome v 119
How to reproduce the bug.
Steps to reproduce:
Clone serenity-js-cucumber-webdriverio template.
Follow installation instructions
Run tests
Serenity/JS version
The text was updated successfully, but these errors were encountered: