Gutenberg Needs Testing Areas

The goal of Gutenberg is to simplify the creation of rich pages and posts in WordPress by replacing old custom HTML, CSS, and shortcodes with native Blocks. Gutenberg development is moving fast right now and there are a few general areas which could use extra help with testing.

If you are here to help, thank you so much! To triage issues that have been reported by others, use the steps for testing bugs in the make/test handbook as a good starting place and guideline. To test in general, see the lists below for ideas about what to test and then either file an issue, post a comment here, or mention your findings in #core-test on WordPress Slack. All testing is welcome!

Some general areas that need testing are:

  1. Everything in the Needs Testing label. Use the steps for testing bugs. 😊
  2. RTL languages.
  3. Roles/Capabilities.
  4. Undo/Redo.

Areas that need testing from a developer perspective:

  1. Everything in the Needs Technical Feedback label. 😊
  2. Backwards Compatibility label.

Testing ideas to help you get started:

  1. Switch to an RTL language and try adding as many different types of blocks as possible.
  2. Switch to an RTL language and test all of the sidebar settings such as categories, tags, changing the publish date, etc.
  3. Create and schedule a new post. Try from a different role.
  4. Create and publish a post with several different blocks using the Editor role.
  5. Create and publish a post with several different blocks using the Author role.
  6. Create and submit a post with several different blocks using the Contributor role.
  7. Add a pending post as one user and try to approve it as another user.
  8. Edit the demo post, make changes, undo and redo the changes as you go.
  9. Edit a page and try making changes and then undoing the changes.
  10. Publish a post with a block type you haven’t used before yet.
  11. Developers: reach out to those with questions at Needs Technical Feedback and chime in if you can confirm a bug or give an alternate code-related solution to a help request. ❤️
  12. If you have an idea about something else to test, add it in the comments!

If you find a new bug, please file it in gutenberg on GitHub. Thank you!

If you are new to testing Gutenberg, the first thing you’ll want to do is get setup for testing with one of the following options:

The stable release is the easiest to test and the local dev env is a bit more technical. Testing any of these will be a great option at this stage. Choose whichever works well for you! If you’re not sure which one to pick, ask and someone will help. 🤓

Any questions? Please ask here or in #core-test on WordPress Slack any time! We would love to see you there.

#call-for-testing, #gutenberg