Call for Testing: Gutenberg 4.0 Pre-release

Gutenberg is currently the main focus for the testing group and it is the new editing experience in WordPress. 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.

To help test, please download gutenberg.zip from the releases page, or use the button above, and try testing any of the following things:

  1. Change the overlay color on the Cover Image block. (10291)
  2. Try changing the style variation and colors for pullquotes. (9763)
  3. Edit a post already being edited by another user and check that post looking works as expected. (4217)
  4. Align different blocks. Try on mobile. (10085)
  5. Turn on the option to skip the publish confirmation and check that posts publish immediately. (9760)
  6. Exit the code editor using the link at top right. Try from different browser versions. (10061)
  7. Nest some bulleted list items and check that the indented ones are circles. (10358)
  8. Search for terms when adding categories. (10138)
  9. Add a text color to a paragraph with links and see that the links change color too. (10171)
  10. Insert images using the classic block. (10306)
  11. Embed a few videos and check that they look correct at different screen sizes. (10161, 10213)
  12. Paste content from Word or LibreOffice and check that unwanted style tags aren’t showing. (10019)
  13. Use access + z (ctrl + option + z on a Mac / shift + alt + z elsewhere) to remove blocks. (10008)
  14. Bonus: test with Yoast SEO.
  15. Bonus: write and publish a few posts while logged as a user with a non-admin role such as editor, author, or contributor.
  16. What else would you like to see tested?!

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

There are a number of updates in this release and you can check the list on the releases page if you’d like to test more or different stuff. If you are a developer creating custom blocks, check out that list for updates that will affect coding.

Block developers: please keep an eye on deprecations in 4.0. Important note:  wp.editor.RichTextProvider is deprecated and is being from Gutenberg in 4.0.0.

Please join us in #core-test on WordPress Slack any time!

Call for Testing: Gutenberg 3.9.0 RC 2

Some updates have been made based on previous testing and issues filed since RC 1 was released.

To help test, please install RC 2 by downloading gutenberg.zip from the releases page or use the button below.

Help is needed testing anything from the list in the Call for Testing: Gutenberg 3.9 Pre-release post or from the following testing list:

  1. Add a classic block, add a latest posts block, save, refresh. (9968)
  2. Add a Vimeo video embed and check for vertical scrollbars. (9920)
  3. Try exporting reusable blocks in IE 11 or Firefox. (10000)
  4. Enable spotlight mode and verify unselected blocks have a lower opacity. (9951)

Please join us in #core-test on WordPress Slack if you have questions or want to bounce ideas around!

#3-9, #call-for-testing, #gutenberg

Call for Testing: Gutenberg 3.9 Pre-release

Gutenberg is the new editing experience in WordPress, and it is currently the main focus for the testing group. 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.

To help test, please download gutenberg.zip from the releases page, or use the button above, and try testing any of the following things:

  1. Select multiple blocks and save them as a reusable block. (9732)
  2. Create, export, import, and modify some reusable blocks. (9788)
  3. Trigger an invalid block warning that says “This block has been modified externally” by modifying the HTML for a paragraph or image block (can you suggest another example for how to trigger an invalid block?) and try out the “Compare Conversion” option in the more menu. (7995)
  4. Find and test the new drag handle in various browsers. (9569)
  5. From a small screen width, test that collapsible toolbar components (such as alignment on paragraph blocks) work as expected. (9687)
  6. Convert a Cover Image block to an Image block and back. (9743)
  7. Open a new post and check whether title field is focused. (9608)
  8. Embed videos with different aspect ratios (16:9, 4:3), check that they look correct. (9500)
  9. Add a gallery as a non-admin role and make sure it loads and is editable. (9875)
  10. Add galleries using IE 11 and Edge. (9622)
  11. Add content using the classic block. (9680)
  12. Find a theme that styles captions for video blocks & make sure styling looks correct. (9609)
  13. Edit a block’s HTML, delete all the content, deselect the block and check that it reverts back to its default state. (9546)
  14. Check that you can insert a Columns block but not a Column (singular) block. (9523)
  15. Use the keyboard shortcut to unlink. (9903)
  16. Bonus: How-to and FAQ blocks with Yoast SEO 8.2  (released Sep 11).
  17. Bonus: write and publish a few posts while logged as a user with a non-admin role such as editor, author, or contributor.
  18. What else would you like to see tested?!

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

Plugin developers: please keep an eye on deprecations in 3.9, especially if you work with colors. Also note that wp.editor.RichTextProvider is deprecated and will be removed from Gutenberg in 4.0.0. Please use wp.data.select( 'core/editor' ) methods instead.

Please join us in #core-test on WordPress Slack any time!

#3-9, #call-for-testing, #gutenberg

Call for Testing: Gutenberg 3.8 Pre-release

There is a new editing experience in WordPress called Gutenberg—it has been a huge team effort and it is currently the main focus for the testing group.  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 3.8 included several improvements and bug fixes and had a short release cycle. There are also a couple test cases from 3.7 thrown in. The testing list tries to cover the major updates as a good starting point for testing.

 

To help with pre-release testing, please download the gutenberg.zip file from the releases page (or use the button above) and try testing the following things:

UPDATE: the following items were added since they made it in to the RC after this post was originally published.

  1. In the top editor toolbar, go to More > Fullscreen Mode and test in that mode. (9567)
  2. Check that the block settings menu works as expected after being moved from the top right of the block to the block toolbar. Note the browser version you tested. (9572)
  3. Add several reusable blocks then bulk delete them. (9588)
  4. Bonus: enable editor styles for a theme you are developing and try writing CSS without adding extra specificity to target the edit area. (9008)

Here is the original testing list:

  1. Drag and drop a block and test that it works as expected: the block being dragged is shown as a grey box, the dragging event shows an image that is a clone of the block being dragged. (9311)
  2. Hover over blocks  and see that the block label appears after a short delay. (9197)
  3. Try to upload a filetype not allowed: `.exe`, empty text file, file w/ no extension. (9578)
  4. Center an image and check that it works as expected on the front end. (9509)
  5. Check that block library icons are aligned properly in various browsers/screen sizes. (9497)
  6. Create a table with 2 columns, remove a column, remove another column. (8767)
  7. Create a table, toggle fixed width table cells, check that alignment works. (8767)
  8. Check to make sure categories still work when the Yoast SEO 8.1.1 plugin is active.
  9. Bonus: test with Yoast SEO 8.1.1 which was released Sep 3.
  10. Bonus: test with WooCommerce 3.4.5 which was released Aug 29.
  11. Bonus: test with Jetpack 6.5 which was released Sep 4.
  12. What else? Are there any major plugins you think should be added to this list?

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

Note for testers/developers: some scripts such as wp.api and underscore are no longer used by Gutenberg. Please keep in mind that plugins should always add their dependencies explicitly when registering scripts, even if it’s already there somehow registered by another script. (9163, 9374)

Please feel free to discuss testing practices or issues here in the comments or in #core-test on WordPress Slack any time.

#call-for-testing, #gutenberg

Call for Testing: Gutenberg 3.7 Pre-release

Gutenberg is the project name of the new editing experience in WordPress. 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. Creating Gutenberg has been a huge team effort – and right now, the team needs your help with testing!

Today, we have a small window for regression testing Gutenberg 3.7 because the release is planned for tomorrow.

If you would like to help with pre-release testing, please install locally so you are using master or download 3.7 as a zip file and install it to your Plugins folder (make sure to delete older versions of the plugin first!), and try testing some of these updates from 3.7:

  1. Write/edit/publish a few posts using the Unified Toolbar (previously called “Fixed Toolbar”).
  2. Change alignment for various images.
  3. Make sure icons and dropdown arrow look correct on hover for block conversion.
  4. Create an Audio block by drag-and-dropping an audio file.
  5. Search for blocks and check that it works as expected (i.e. start with `/` via the inserter).
  6. Convert a multiline-paragraph into a list.
  7. Add links to text.
  8. Add a link by selecting a URL and clicking the link icon.
  9. Upload an image with a space in the filename and check that the title does not have a hyphen added.
  10. Add a post image in a video block.
  11. Add videos and check that all works as expected.
  12. There were several other improvements and bug fixes in the 3.7 release and this list tries to cover the more major updates so we can have a good starting point for testing. Alternately, just run a general test writing or editing posts and pages as you would normally!

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

Please feel free to discuss testing practices or issues here in the comments or in #core-test on WordPress Slack any time.

#3-7, #call-for-testing, #gutenberg