-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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: Handle upgrade screen #28592
Conversation
Size Change: 0 B Total Size: 1.37 MB ℹ️ View Unchanged
|
There are e2e failures, but I believe that they're unrelated (and should be fixed by #28638). I'll rebase this PR now. |
aad4555
to
bd77454
Compare
Hmmm...the e2e tests with Here's an example of the URL we're visiting: I've confirmed that the selector we're using to click on the update button exists. |
@jeyip Silly question, did you run |
I didn't! Lemme give that a shot after I get back from lunch 👍 Just to be safe, I'll destroy and rebuild the current WordPress docker instance as well. |
Blowing everything away and re-rerunning specs fixes the issue |
Description
E2E tests might get stuck on the "Database Update Required" screen. This PR takes care of the screen by automatically clicking on update.
How has this been tested?
The quickest way is to change the
db_version
option in the database.at
gutenberg/gutenberg.php
Lines 17 to 19 in cdc34fb
npm run test-e2e -- --puppeteer-interactive
)Screenshots
Types of changes
Bug fix (non-breaking change which fixes an issue)
Checklist: