Insert Block command

[cadic]

Description of the Change

Adds insertBlock command. Yields the block element ID:

cy.insertBlock('core/heading').then(id => {
  cy.get(`#${id}`).click().type(heading);
});

Tests include custom block from 10up/retro-winamp-block, it doesn't support WordPress 5.2, so this test is optional.

Checklist:

• I have read the CONTRIBUTING document.
• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my change.
• All new and existing tests passed.

Changelog Entry

Added - insertBlock command

Credits

Props @cadic

[cadic]

@dinhtungdu before this PR goes to review I have question:

This PR adds "Insert Block" command and is tested against different built-in block types, including sub-blocks (core/embed/twitter and core/post-navigation-link/post-next). It will be also great to include test of a custom block, but in this case our example WordPress plugin will grow and definitely needs to be moved to a directory. I think this is required because custom blocks are handled a bit different in the core (f.e. the selectors are different).

Do you think it worth to be done or we could keep core-only blocks in our test?

[dinhtungdu]

It will be also great to include test of a custom block, but in this case our example WordPress plugin will grow and definitely needs to be moved to a directory.

@cadic This is a blocker to me as well.

Do you think it worth to be done or we could keep core-only blocks in our test?

I think as long as we pass the correct block name, there is no difference between core and custom blocks. So my answer to your question is no, I don't think it's worth adding a custom block to our example plugin.

On the other hand, we can test inserting custom blocks without creating our own. I think any simple block plugin in the block directory can be used for our testing.

[cadic]

@dinhtungdu thank you for the idea of using external plugin for custom blocks. Added https://github.com/10up/retro-winamp-block/ and it works like a charm!

[dinhtungdu]

Overall, this is LGTM! But I have an issue with the custom block test for WP 5.9.3: the custom block test was skipped. The Winamp block was there but wasn't inserted into the editor:

[cadic]

@dinhtungdu thank you so much for checking the tests on your side. The command itself is fine, but the test has a typo in its conditional part which caused skipping the test when it should be executed.

[dinhtungdu]

LGTM 🚢