Call for Testing: Gutenberg 4.3 Pre-release

This releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. will have a short turnaround time for testing in order to allow the pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. code to get better aligned for merging.

The goal of GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ is to simplify the creation of rich pages and posts in WordPress by replacing old custom HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites., CSSCSS CSS is an acronym for cascading style sheets. This is what controls the design or look and feel of a site., and shortcodes with native Blocks. The Gutenberg plugin is currently the main focus for the testing group and Gutenberg is the new editing experience in WordPress

To help test, please download gutenberg.zip from the releases page or use the button above, install/activate the plugin, and try testing any of the items listed below. If you don’t have time to test everything on the list, try just doing a few items. All testing is welcome!

  1. Add several blocks with various alignments (left, right, center) and check to make sure the toolbar appears properly for each one. (11357)
  2. Press meta+A to select a blockBlock Block is the abstract term used to describe units of markup that, composed together, form the content or layout of a webpage using the WordPress editor. The idea combines concepts of what in the past may have achieved with shortcodes, custom HTML, and embed discovery into a single consistent API and user experience. and meta+A again to select all blocks. Test with Safari and Firefox. (8180)
  3. Test the sibling inserter with Firefox and Safari. (11684)
  4. Create a new post and start typing for at least 10 seconds. Verify that autosave does not occur while typing and that autosave does occur after 10 seconds of no action. (10103)
  5. Add a pullquote and change the colors in various ways. Make sure the text is readable. (10792)
  6. Add a Media & Text block, select the “Stack on mobile” option, publish and view on mobile and see that the blocks are responsive. (10969)
  7. Create a Google Docs document with text that is both bold and italics and that has text with strikethrough, subscript, and superscript. Copy and paste the content into the editor and check that the formatting is correct. (11207)
  8. Drag and drop multiple files into the editor and check that file blocks are created for each one. (11297)
  9. Insert a thumbnail-sized image and set the link settings to media file. Check that clicking on the image from the published post opens the full-sized image. (11254)
  10. Change the permalink for an existing post and save changes. Make sure the “View as” link in the black toolbar at the top works as expected. (11262)
  11. Try opening a draft or a previously published post, do not make changes, close the browser tab—make sure you are not prompted to save changes if you opened a post and did not make any changes. (4687)
  12. Activate a dropdown item, such as the inserter, and click outside of it to close the dropdown. (11253)
  13. Add a YouTube URLURL A specific web address of a website or web page on the Internet, such as a website’s URL www.wordpress.org to a video block and make sure it gets added as a working YouTube embed. (6824)
  14. Schedule a post and make sure it works as expected. (11418)
  15. Transform a Media & Text block to a video or image block and vice versa. (11420)
  16. Convert a classic block to blocks with e.g. a span with attributes in a paragraph. (11539)
  17. Upload ~10 large (10 MB) images into a gallery and see that they upload without error. (11565)
  18. Use Alt+F10 to navigate to the block toolbar (not the editor toolbar). (11607)
  19. Add a columns block with various content. (11620, 11659)
  20. For more, see issues in the 4.3 milestone.

AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) Related

These are accessibility-related testing steps, though anyone can help test these!

  1. Publish a post using the keyboard only (4187).
  2. Navigate through the images in a gallery using the keyboard. Try different browsers. (11205)
  3. Add a link to another existing post from your site using the keyboard only. (10838)
  4. Using a screen reader, add a link, search for a post, select a link, and check that the result is announced. (10838)
  5. Using a screen reader, select multiple blocks, and check that the number of blocks selected is read out. (11422)

Bonus Round

You should test these if you’re willing to dig in a little deeper, if you know of (or can find) custom plugins that use some of the updated capabilities, or if you would like to help test Gutenberg with popular plugins.

  1. Go to More > Options and check the option for Custom Fields. Check that custom fields work as expected. (11084)
  2. Add a left aligned and a right-aligned image to a post. Switch the site to use an RTL language and check that the alignments are the same. (11293)
  3. Add a bunch of metaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. boxes and check to make sure the editor still has ample room. (11482)
  4. Find a plugin that removes the “kitchen sinkKitchen Sink When using the WYSIWYG (What You See Is What You Get) editor in WordPress, you can expand the capabilities to allow more options. This expanded area is called the "Kitchen Sink."” button from the old editor and confirm it works as expected. (10964)
  5. Install a plugin that uses the SlotFill APIAPI An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. (for example: DropIt or Yoast SEO) and make sure it works as expected. (11123)
  6. Test with Advanced Custom Forms (ACF).
  7. Test with Yoast SEO.

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

Block developers: make sure to be aware of deprecations.

Please join us in #core-test on WordPress Slack any time if you have questions about testing!

#4-3, #call-for-testing, #editor, #gutenberg