designsimply 6:08 pm on December 12, 2018
Tags: 4.7, ,   

Call for Testing: Gutenberg 4.7

This Gutenberg release includes several bug fixes and focuses on improving the performance of the block editor, particularly when editing large posts. It will line up with WordPress 5.0.1 and can be first tested as a plugin version 4.7.

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. The Gutenberg plugin is currently the main focus for the testing group and Gutenberg is theĀ new editing experience in WordPress.
Download 4.7.0
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. You can also see other options for getting setup for testing in the handbook. Currently, you should be testing with WordPress 5.0 stable alongside the Gutenberg 4.7 plugin. This is becauseĀ 5.1-alpha trunkĀ is currently undergoing some cleanupĀ (normally, testing with trunkĀ is fine). All testing is welcome even if itā€™s just one or two items!
  1. Create a very long post with thousands of words. (12480)
  2. Open a very long post and begin typing to add new content. (12386, 12460, 12521, 12547)
  3. Create a large post with many different types of blocks. (12384, 12510)
  4. Add an image to the Media & Text block and try to resize the image. (12619)
  5. Add an image by selecting one from the media library, click undo, and make sure the placeholder shows properly at that point. (12567)
  6. Copy and paste content from one block to another. Switch to Code Editor mode. (12543)
  7. Insert several images into a classic block and make sure they are inserted into the correct location where the cursor was positioned. (10509)
  8. Try tabbing through blocks and check to see if it works as expected even after pressingĀ Ctrl + backtickĀ twice to jump to the top toolbar and back to the content area. (12390)
  9. Create, delete, add, then trash a reusable block. After it is trashed checked to see that a ā€œDeleted or unavailableā€ message appears in its place in the editor.Ā (12345)
  10. Copy content from a word processing app and confirm no spaces are collapsed unexpectedly. (12166)
  11. Edit a paragraph as HTML. Remove a space and insert a line break (use ENTER). Edit visually. You should see a space where you inserted the line break. Edit the content. Edit as HTML. The line break should be replaced by a space. (12166)
  12. Disable a core block, try pasting content that will trigger that block, expect it to. (11057)
  13. InstallĀ ACFĀ and make sure hidden meta boxes stay hidden. (12628)
  14. Install a plugin which uses TinyMCE in a textareaĀ in a meta box area, such asĀ Memberlite ElementsĀ or Meta Box (and can you think of any others we can test?), then create a post using that content and make sure it saves. (12568)
  15. For more, seeĀ issues in the 4.7 milestone.
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-7, #call-for-testing, #gutenberg

designsimply 7:28 am on December 6, 2018
Tags: , , , popular plugins   

Call for Testing: Gutenberg + Popular Plugins

Calls for testing WordPress 5.0 beta have been running since Oct 24, and the release is right around the corner. While we have highlighted a few plugins to test in past calls for testing here on make/test, it was pointed out that more plugin testing would be helpful to have and so letā€™s add it in!

Plugins that are most likely to have compatibility issues are those that modify the the interface of the post edit screen, perform actions on post update/save or add custom taxonomies.Ā /hat tip @gschoppe via https://twitter.com/gschoppe/status/1070344946643816448
To help test, you can install and activate the WordPress Beta Tester plugin on a test site, select ā€œBleeding edge nightliesā€ from the Tools > Beta Testing page and then click ā€œUpdate Nowā€ on the Dashboard > Updates page in wp-admin. From there, pick any plugin from the list below and see what you can break. šŸ™‚ If you find a plugin conflict between the plugin you are testing and Gutenberg, the very best place to report it is to the plugin developer directly. Each plugin has a support forum available by using the Support tab at the top of the plugin directory page. You may also report plugin conflicts to the gutenbergĀ repository on GitHub where you will likely get more help testing and advice on where and how to report back to the plugin author if needed. To start, Iā€™ve picked a handful of plugins either because they seem like good candidates from the popular plugins listĀ or have been mentioned inĀ Ā gutenbergĀ on GitHub or on this blog:
  1. Yoast SEO
  2. Advanced Custom Forms
  3. Wordfence
  4. Elementor
  5. Contact Form 7
  6. WPForms
  7. NextGEN Gallery
  8. Divi Theme
There are many more plugins to test, and suggestions are welcome if you think any should be added to this list. This list should be considered a starting point and anything from the first four pages of theĀ popular plugins listĀ would also be good toĀ consider for testing. If you are able to help test, pick something you like, or that looks interesting to you, or (even better!) that you use on your own site. It is worth noting that several of these plugins have been tested already and many developers have been working hard on updates along the wayā€”some even include custom Gutenberg blocks. This call for testing is an extra way to try to provide help for those developers. If you are a plugin developer and would like to add your plugin as a suggested addition for testing, it would be helpful to provide a link and a short list of testing ideas or steps to help testers get oriented with your work. Please leave a comment if youā€™re interested!

#call-for-testing, #gutenberg, #plugins, #popular-plugins

designsimply 12:43 am on November 10, 2018
Tags: , , ,   

Call for Testing: Gutenberg 4.3 Pre-release

This release will have a short turnaround time for testing in order to allow the plugin and core code to get better aligned for merging.

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

Download Gutenberg v4.3.0-rc.1

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 block 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 URL 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.

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 meta boxes and check to make sure the editor still has ample room. (11482)
  4. Find a plugin that removes the ā€œkitchen sinkā€ button from the old editor and confirm it works as expected. (10964)
  5. Install a plugin that uses the SlotFill API (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

designsimply 6:44 pm on October 31, 2018
Tags: , , , ,   

Call for Testing: Gutenberg 4.2 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.

Download GutenbergĀ v4.2.0-rc.1

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 (or anything listed in the 4.2 release notes). Testing even just a few items is helpful. All testing is welcome!

  1. In block toolbars, check that all writing formatters (e.g. bold, italic, link, strikethrough) work as expected. Try both clicking and keyboard shortcuts. Try from different browsers.Ā (10209)
  2. Add several blocks and use the sibling inserter to add new blocks between them. Try from different browsers. (11018, 11243)
  3. Add new categories to a post. Save draft. Refresh. Are categories added as expected? (10089)
  4. Type some text into a paragraph block and check that pressing Escape makes the block toolbar appear (note: Unified Toolbar mode should be off for this test). (10906)
  5. Type /imgĀ into a new block and check that the image block appears as an option. (10955)
  6. Add the Latest Posts block, toggle ā€œDisplay post dateā€ on, publish or preview the post and check that the has-datesĀ class appears in the source code both in the editor and on the front end. (10727)
  7. Using a small screen (mobile), check that you can open and close the Options panel from More menu (three dots, very top right) > Options (near the bottom). (10894)
  8. Add an image, add a link for the image (sidebar near the bottom), toggle ā€œOpen in New Windowā€ on, publish the post and check that a new window opens when you click on the image.Ā (9520)
  9. Add a button block and change the background and text color. Do the color changes work as you expected? (10658)
  10. Add a file block, attache a file, publish the post, and check that the ā€œDownloadā€ button works normally.Ā Try different types of files. (10976)
  11. Turn on Unified Toolbar mode. Add aĀ Media & Text block and check that you can resize media. (10913)
  12. Add a classic block and include some inline images, links, bold text, italic text and try modifying each of those after making edits throughout.Ā  (10723)
  13. Using a small screen (mobile), log in as a contributor, submit a post, and make sure the ā€œSubmit for Reviewā€ button appears. (10941)
  14. General: performance improvements were made to toolbars, inserters, and the classic block. Did you notice the changes? (ref)
  15. General: some descriptions of blocks and options in block settings have changed. If you spot one that doesnā€™t make sense to you, leave a note in the comments here or ask about it in #core-editor on Slack.
  16. General accessibility: in the WP Admin main menu on the left, go to Gutenberg > Demo and try to navigate to the pullquote block using the keyboard. Did keyboard navigation work as expected for you? Why or why not? Add notes for this one to the comments here and I will pull details and compile them for a succinct issue if needed. šŸ™‚
  17. There is more to test! See Whatā€™s new in Gutenberg? (30th Oct)Ā .

Accessibility Related

I wanted to call out accessibility-related testing steps this time in order to highlight some of the important accessibility updates coming through right now and because it may make sense to group them together while testing. Anyone can help test these!

  1. Type some text into a paragraph block and check that the toolbar shows when you press Escape. (10906)
  2. Add aĀ Media & Text block with an image and change the alt text for the image. (11073)
  3. Open the sidebar, click ā€œDocumentā€, pressĀ Tab, pressĀ Spacebar, check that the ā€œBlockā€ tab is still focused. (10917)
  4. Using a screen reader (if you have a Mac you can use VoiceOver and Safari), open the block inserter, search for a block, and check that you hear an audible response for the number of search results or ā€œno resultsā€. (10755)
  5. Using a screen reader (if you have a Mac you can use VoiceOver and Safari): add, edit, and then remove a link and check that those actions are announced audibly. (10795)

Bonus Round

Iā€™m also adding a separate section as an optional bonus round for testing. You should test these if you know of (or can find) custom plugins that use some of the updated capabilities (such as registering new toolbar buttons in blocks) or if you would like to help test Gutenberg with popular plugins. If you think of a plugin youā€™d like to see added, please comment to note it!

  1. Add a WordPress embed and check that there is not a big empty space after the block. (10985)
  2. Find a plugin that adds buttons to any block toolbar and check that the added buttons are working as expected. (11196)
  3. i18n: using a small screen (mobile) and with the site language set to something other than English, log in as a contributor, submit a post, and make sure the ā€œSubmit for Reviewā€ button appears. (10941)
  4. i18n: change your site language to something other than English and check that taxonomy panels display localized strings. (8449)
  5. i18n: install a plugin which contains a block name made in a non-Latin script (e.g.Ā Š”ŠæŠøсŠ¾ŠŗĀ for the List block in Russian) and check that the block appears when you type /сŠæ into a new block. Note that searching for names with diacrytics should also work. (10961, 10770)
  6. Plugin developers can now disable post publishing (lock the post) if certain conditions arenā€™t met such as a required a minimum title length, requiring a featured image, disallowing certain types of content, etc. If you have a plugin which has a pre-publish lock or checklist, can you note it in the comments with testing steps? šŸ™‚ (10649)
  7. Test withĀ Advanced Custom Forms (ACF).
  8. Test withĀ Yoast SEO.

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

Block developers: note that there are several deprecations in 4.2 to keep an eye on. It is also noteworthy that you can now write a format that is usable across all blocks that use RichTextĀ (10209).

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

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

designsimply 11:50 pm on October 19, 2018
Tags: 4.1, , ,   

Call for Testing: Gutenberg 4.1 Pre-release

The feature-complete version of Gutenberg (4.1) is now ready for pre-release testing! 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.

UPDATE: Links have been updated to 4.1 RC 2 as ofĀ Oct 22, 2018, 12:11 PM UTC.

Download Gutenberg v4.1-rc.2

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 (or anything listed in the 4.1 release notes). Testing even just a few items is helpful. All testing is welcome!

  1. Move around in a long post or page using block navigation. (10545)
  2. Add a video background using the Cover block. Try different browsers. (10659)
  3. Add a table block and change the style variation to striped using the Settings > Block sidebar. (10428,Ā 10543)
  4. Use the Media & Text block to add side-by-side media and text. (9416)
  5. Resize things in theĀ Media & Text block in various ways.Ā Ā (9416)
  6. Accessibility: test the date picker. (7621)
  7. Accessibility: test the color picker using keyboard navigation. (10564)
  8. Check that each setting in More > Options works and persists when the page reloads. (10215)
  9. Add a list block and try pasting both single lines and multiple lines into it. (10614)
  10. Insert an image using a URL. (9264)
  11. Switch to an RTL language and try the LTR toggle button in the paragraph block. (10663)
  12. Add a quote block, convert it to a pullquote, convert it back to a quote. (10683)
  13. Add a quote block with a citation, convert it to a paragraph block, make sure the citation is still there. (10685)
  14. Embed some YouTube videos and make sure they look as expected in the editor and after publishing. (10411)
  15. Test the custom color picker for the button block on mobile. (10481)
  16. Test the responsiveness of the Columns blockā€”still designated beta but improvements have been made, try just a few columns for now. (10541)
  17. Enable or disableĀ Advanced PanelsĀ (AKA Meta Boxes) using More > Options. (10215)
  18. Bonus: test withĀ Advanced Custom Forms (ACF) and check that you can toggle the Custom Fields meta box on/off using the More > Options panel.Ā (10676)
  19. Bonus: test with Yoast SEO.
  20. There is more to test! See Whatā€™s new in Gutenberg? (19th Oct) and general needs-testing.

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

Block developers: note theĀ deprecation in 4.1:Ā wp.data.dispatch( 'core/editor' ).checkTemplateValidityĀ has been removed. Please look ahead and keep an eye onĀ deprecations in 4.2 as well! There are several coming up as prep for merging with WordPress 5.0 is now underway.

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

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

designsimply 12:39 am on October 19, 2018
Tags: ,   

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

designsimply 7:16 pm on October 10, 2018
Tags: 4.0, , ,   

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.

Download Gutenberg v4.0-rc.1

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!

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

designsimply 6:49 pm on September 19, 2018
Tags: , , ,   

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.

Download Gutenberg v3.9.0-rc.2

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, #editor, #gutenberg

designsimply 7:52 pm on September 14, 2018
Tags: , , ,   

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.

Download GutenbergĀ v3.9.0-rc.1

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, #editor, #gutenberg

designsimply 3:01 pm on September 5, 2018
Tags: , ,   

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.

Download Gutenberg v3.8.0-rc.1

Ā 

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, #editor, #gutenberg