Gutenberg 7.2.0: Update E2E tests

[mmtr]

Changes proposed in this Pull Request

Updates some CSS selectors and texts in order to match the new classes and sentence case changes introduced in Gutenberg 7.2.0.

[matticbot]

Test live: https://calypso.live/?branch=try/gutenberg-7.2.0-e2e

[mmtr]

Seems that tests are currently failing due to WordPress/gutenberg#19050

Some classes have changed so we need to update the selectors.

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

App Entrypoints (~140567 bytes removed 📉 [gzipped])

name        parsed_size            gzip_size
entry-main    -639110 B  (-39.8%)  -140567 B  (-35.9%)

Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used.

Sections (~46051 bytes removed 📉 [gzipped])

name             parsed_size             gzip_size
post-editor        -627968 B   (-32.8%)  -156776 B   (-30.0%)
reader             +547244 B  (+139.2%)  +137482 B  (+136.3%)
theme              -139480 B   (-35.3%)   -30798 B   (-31.5%)
media              +138863 B   (+37.9%)   +22218 B   (+23.1%)
marketing          -106563 B   (-25.1%)   -21476 B   (-20.8%)
home                 +6402 B    (+2.5%)    +2322 B    (+3.5%)
themes               -2785 B    (-0.9%)     +329 B    (+0.4%)
plugins              -2785 B    (-0.6%)     +329 B    (+0.3%)
hosting              -2785 B    (-1.2%)     +329 B    (+0.5%)
jetpack-connect      -1733 B    (-0.3%)      -10 B    (-0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[mmtr]

Uhm, not sure why the new step is currently failing with Timed out waiting for element with css selector of '.customer-home__layout button[data-e2e-action="update-homepage"]' to be clickable.

When running Calypso locally, that selector is valid, so I wonder if the test is running against a stale image.

[Stojdza]

@mmtr I tried Basic sign up for a free site @signup @email @ie11canary test locally against WP.com and against live branch from this PR. The result - test is passing against live branch and it's failing against WP.com. Which is expected, since data-e2e-action="update-homepage" is introduced in this PR.

That's why I added [Status] Needs e2e Testing label to see what will happen. Tests triggered with this label will run against live branch for sure, and Basic sign up for a free site @signup @email @ie11canary has passed. My assumption that tests triggered with edge label don't run against live branch. Instead, they run against WP.com and that's the reason why it fails. I will take a look at this problem in the next days. You're good to go with these changes 👍

Differences from CircleCI:

[Status] Needs e2e Testing Gutenberg Edge label:

[Status] Needs e2e Testing label:

[mmtr]

Awesome, thanks for clarifying @Stojdza!

[kwight]

Can we keep the new revisions test in a separate PR, and have this PR remain only what's needed to get the plugin updates to pass?

[kwight]

Love it <3

[mmtr]

Can we keep the new revisions test in a separate PR, and have this PR remain only what's needed to get the plugin updates to pass?

Thanks for the suggestion @kwight. Small PRs for the win!

Moved all new steps and tests that are unrelated to the Gutenberg update to separate PRs:

• Check homepage during sign up: E2E: Check homepage can be edited on Gutenberg after sign up #38765
• Check revisions modal: E2E: Check revisions modal on Gutenberg #38766
• Check Jetpack blocks: E2E: Check Jetpack blocks on Gutenberg #38767

[mmtr]

We needed to remove the basic publish post test from the IE11 canary test suite since it was failing and we didn't want to block the Gutenberg update.

We'll investigate later what was causing the failure.