"Login as editor" as an example for testing user roles

[bacoords]

This was a blueprint that @adamziel helped me with a while back and I think it'd be useful for others. I use it when quickly testing the Gutenberg feature differences between editor / administrator.

It was unclear in the instructions whether I should run the reindexing in my PR or not.

Related WordPress/wordpress-playground#1129

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• The Plugin and Theme Directories cannot be accessed within Playground.
• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[adamziel]

Looking good, thank you @bacoords!

It was unclear in the instructions whether I should run the reindexing in my PR or not.

No need, CI does that automatically. How would you adjust the instructions to make that clearer?