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
E2E tests are failing locally and in CI #37
Labels
Comments
This was referenced Apr 26, 2024
I updated #38 to upload the Playwright traces. They can be downloaded individually and inspected with
Here's what the one "create a new site" shows: Two things to notice:
|
I have a crude fix for the onboarding issue at |
Merged
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Quick summary
The E2E tests are currently failing, both locally and in CI.
I think the reason this hasn't been noticed in PRs is that the workflow step is configured with
continue-on-error: true
.Steps to reproduce
Locally, run
npm install && npm run package && npm run e2e
.On CI, visit a recent PR and look at its actions. For example, #56: https://github.com/Automattic/studio/actions/runs/8830011430/job/24242246592?pr=27
What you expected to happen
E2E tests should be able to create tmp sites and move forward with the testing.
What actually happened
Locally, you can see the app being stuck on the "Add your first site" screen:
I assume the same happens in CI, based on the way the tests fail, but I have no way to verify it.
Impact
One
Available workarounds?
There is no user impact
Platform
No response
Logs or notes
Here's my local test log
The text was updated successfully, but these errors were encountered: