Skip to content

Playwright testing does not work out of the box. #7825

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

Closed
damiensedgwick opened this issue Nov 27, 2022 · 0 comments · Fixed by #7826
Closed

Playwright testing does not work out of the box. #7825

damiensedgwick opened this issue Nov 27, 2022 · 0 comments · Fixed by #7826

Comments

@damiensedgwick
Copy link

Describe the bug

When creating a new Sveltekit project, Playwright testing does not work out of the box.

Reproduction

For ease, I have created this repo specifically to clone down and test the issue Issue Repo

Steps for reproduction:

  • Create a new Sveltekit project npm create svelte@latest my-app
  • Install the projects dependancies npm i
  • Try to run the default test npm run test

Logs

npm run test

> [email protected] test /Users/damien.sedgwick/Development/sveltekit-playwright-testing-issue
> playwright test

(node:10328) ExperimentalWarning: Custom ESM Loaders is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

Running 0 tests using 0 workers

=================
 no tests found.
=================

 ELIFECYCLE  Test failed. See above for more details.

System Info

System:
    OS: macOS 13.0.1
    CPU: (8) arm64 Apple M1 Pro
    Memory: 285.05 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.12.0 - ~/.nvm/versions/node/v18.12.0/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.0/bin/npm
  Browsers:
    Chrome: 107.0.5304.110
    Safari: 16.1
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.89
    @sveltejs/kit: next => 1.0.0-next.562
    svelte: ^3.44.0 => 3.53.1
    vite: ^3.1.0 => 3.2.4

Severity

annoyance

Additional Information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant