PW Spec Migration: Gutenberg block upgrading

[dpasque]

Details

On the selenium framework, wp-calypso-gutenberg-upgrade-spec.js tests how block markup goes through the upgrade by copying markdown from popular blocks and pasting them onto an edge site.

We have this covered in part by all the new block smoke test cases. However, this doesn't cover breakages caused by the block markdown going through the upgrade transformation.

We should add a new spec that takes an existing post on a Gutenberg edge site and checks that there are no new errors post upgrade. This could start by checking the editor for block errors. In the future, we could also diff screenshots.

Checklist

• [ ] Make the static post on a Gutenberg edge site
• [ ] Make script to validate it is error-free post-upgrade
• [ ] Potentially make a bin script that uses the Playwright POM library to "regenerate" the post -- delete all the block content and configure all the needed blocks. This could be run whenever something gets busted with the post data over time.

Related

No response

[dpasque]

@fullofcaffeine You had mentioned interest in tackling this script -- still interested? I would love to help out however I can! I can also walk through some of the new block classes we have that might help with making the bin script that could regenerate the post.