Automated Testing

Due to the rapid iterations of Gutenberg, and how this plugin uses it in ways that might be otherwise untested, it would be ideal if this plugin had automated testing running.

The tests could run both post-commit, but also on a daily schedule against Gutenberg trunk, to detect issues before the next release of the plugin is made.

This would help greatly with sites, such as WordPress.org/support, which runs both the latest WordPress trunk, Gutenberg Release, and Blocks Everywhere.

Start by examining the plugin's existing test setup and CI configuration, then review how it integrates with Gutenberg. Define a post-commit run and a daily run against Gutenberg trunk, with failures visible before plugin releases; verify the workflow against the WordPress.org/support environment.

Written by the indexing model from the issue text.