Calling all testing plugins

You might have noticed a new section on this site’s sidebar for ‘testing plugins’. The idea is to feature all the testing plugins used throughout the WordPress project.

Current testing plugins:

Did I miss any plugins? If you know any please leave a comment and we can add them to the list in the sidebar.

#testing-plugins

Gutenberg Usability Testing for August 2019

August usability testing has come to an end. I ended with 5 videos this month! The script was new and encouraged the users to build a mobile phone landing page. It focused on the Column block and Cover blocks.

Testing script

Imagine you work for an industrial design company. The company has just created a new mobile phone. You’ve been assigned to create a beautiful landing page for this new phone. To do this, you will be using WordPress’ new Block Editor. Please make sure to talk through everything out loud as you complete the tasks. Let’s get started.

  1. Log in.
  2. Create a new post.
  3. Give your post a title.
  4. Add an image of a mobile phone. Once the image has been added, set the block to be full width.
  5. Below that add a Heading block with the text, “Features.”
  6. After that, add a Column block with three columns.
  7. Add a feature to each of the columns. You’ll first add an image, then a heading below that and some text below the heading. See the next task for details.
  8. In the first column add an image, under that add a heading that says, “Pixel Perfection Photos”, under which you’ll add the text, “Our camera is packed with pixels. Take beautiful high quality pictures.”
  9. In the middle column add another image, and a heading that reads, “Chrystal Clear Communication” with some text below that reads, “The sound coming from our speakers will leave you feeling like the other person is right there.”
  10. In the last columns, add another image, then add a heading, “Ubiquitous” with text below that reads, “Our phone is offered by all the major carriers.”
  11. Below this Column block, add a Cover block with a background image. On top of the image write, “Order a phone today!” and then add a Button block that says, “Order today”.
  12. Under the Cover block, add a Media + Text block with an image on the right and some text on the left that reads, “This phone is loved by everyone.”
  13. Add one more Cover block with an image, but this time set it to be a fixed background.
  14. Now, let’s add a Paragraph that reads, “Many smartphone makers save their best features for their priciest (and largest) devices. Not us. Our new phone includes great features like solid battery life and excellent performance, which means you don’t have to spend $1,000 to get the best smartphone.”
  15. Finally “Preview” your post and make any necessary changes you think are important.
  16. Once you’re ready, Publish your post.

Videos

Video 1 – Aug 1st

Add a heading block? How can I do that? I don’t even know what that means.

[After using the search feature in the Block Library] Oh, here it is, actually. I found it.

Video 2 – Aug 8th

Ooops, I did something wrong. How do I remove this?

This looks really really good. I didn’t expect it to look that good. It was that easy.

Video 3 – Aug 14th

That was quite intuitive. Click on the Heading option obviously from this menu.

This appears to be 3 columns, let’s click on that.

[while clicking through the Block Library accordions] I’m not seeing button so far…

Video 4 – Aug 21st

Things seem to be easy to find.

Video 5 – Aug 28th

To set to full-width, I’m just gonna drag it out.

It’s getting a lot faster now that I’ve done this once. It’s way easier!

Feedback

As with all the prior videos being shared, please leave some feedback! What are some patterns that pop out to you? What successes do these users have in navigating and creating a post? What challenges become evident in their flow?

As a reminder, if you’re interested in helping with usability testing, there’s a number of things you can try:

  • Join the #research channel in slack.
  • You can write a test script that can be usability tested for Gutenberg.
  • Or simply watch the videos and leave some feedback below.

Thanks for watching and contributing anywhere you can.

#gutenberg, #usability-testing

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

WCEU usability test results: part one

During WCEU there were a number of usability tests run. For each test, there was a form to follow through and questions. In this first part, five videos will be shared with the answers, then a second post with another five will be made. Thank you every person that both helped run tests and also took part in them. It’s really important to have opportunities to test like this.

As you watch through have a think about a few things:

  • What bugs or enhancements could be made from this?
  • What insights do you gain in the way people use Gutenberg?
  • Any ideas that spring up from this of ways to make the editor even better for people?

Share anything you have as a comment and part two will be along in a few days.

Continue reading

#gutenberg, #usability-testing, #wceu-usability-testing

Gutenberg Usability Testing for June 2019

Continuing the usability tests on Gutenberg, here’s three from the month of June. The insights found in these videos help inform decisions going forward with Gutenberg. Keep in mind that due to the platform being used for these videos, many of the users might be completely new to WordPress.

This month focused on a test similar to the WCEU usability tests that were run. You can read up on those from WCEU here: part one and part two. It focused on building a post using common blocks including media + text, headings, etc.

Testing script

Imagine you’re writing a blog post about your favorite bakery. Your blog should have a title, some images of desserts, and a couple content sections. Please make sure to talk through everything out loud as you complete the tasks. Let’s get started.

  1. Log in.
  2. Create a new post.
  3. Give your post a title.
  4. Add a Cover block to your post with a message overlaying the image that reads, “The sweetest place on earth”.
  5. Make the Cover block full-width.
  6. Add a paragraph below that reads, “This bakery is committed to using the finest ingredients from all over the world ensuring that quality remains the cornerstone of their business. In fact, quality is the number one ingredient in everything they do.”
  7. Now add a heading for the cupcakes section.
  8. In this section, add an image of cupcakes with some text along the right side of it.
  9. Add a sentence or two below to finish off the cupcake section.
  10. Add a new heading about cookies.
  11. In this section, add a Media+Text block with an image of cookies on the right, and some text on the left side. Make this area full width.
  12. Below that, add a gallery of 5 more images.
  13. Now add a quote you heard someone say about this bakery. Maybe something like, “This bakery is almost as good as Grandma’s house!”
  14. At the bottom, add a horizontal divider.
  15. Finally, include a link to the bakery site. Type the bakery name, and then link it to a website (any website is fine).
  16. Publish your post.

Videos

Video 1 (June 5, 2019)

I’m not sure how I’m supposed to make it go on the right.

I want to add a paragraph so I’ll just write some lines.

Video 2 (June 13, 2019)

I’m not sure how to do that but I’m going to give it a try.

I cannot figure out for the life of me how to get the writing exactly right next to it.

Video 3 (June 25, 2019)

This looks good!

How do I add an image?

Feedback

As with all the prior videos being shared, please leave some feedback! What are some patterns that pop out to you? What successes do these users have in navigating and creating a post? What challenges become evident in their flow?

As a reminder, if you’re interested in helping with usability testing, there’s a number of things you can try:

  • Join the #research channel in slack.
  • You can write a test script that can be usability tested for Gutenberg.
  • Or simply watch the videos and leave some feedback below.

Thanks for watching and contributing anywhere you can.

#gutenberg, #usability-testing

Gutenberg Usability Testing for July 2019

July usability testing has completed for Gutenberg. I kept the same testing script as last month to be able to make a comparison over the course of these last two months. The users were mostly new to WordPress so expect a novice level of interaction.

Testing script

Imagine you’re writing a blog post about your favorite bakery. Your blog should have a title, some images of desserts, and a couple content sections. Please make sure to talk through everything out loud as you complete the tasks. Let’s get started.

  1. Log in.
  2. Create a new post.
  3. Give your post a title.
  4. Add a Cover block to your post with a message overlaying the image that reads, “The sweetest place on earth”.
  5. Make the Cover block full-width.
  6. Add a paragraph below that reads, “This bakery is committed to using the finest ingredients from all over the world ensuring that quality remains the cornerstone of their business. In fact, quality is the number one ingredient in everything they do.”
  7. Now add a heading for the cupcakes section.
  8. In this section, add an image of cupcakes with some text along the right side of it.
  9. Add a sentence or two below to finish off the cupcake section.
  10. Add a new heading about cookies.
  11. In this section, add a Media+Text block with an image of cookies on the right, and some text on the left side. Make this area full width.
  12. Below that, add a gallery of 5 more images.
  13. Now add a quote you heard someone say about this bakery. Maybe something like, “This bakery is almost as good as Grandma’s house!”
  14. At the bottom, add a horizontal divider.
  15. Finally, include a link to the bakery site. Type the bakery name, and then link it to a website (any website is fine).
  16. Publish your post.

Videos

Video 1 (July 4)

[User adds a Cover block] Okay, now I’m just going to begin typing in it. [completely skips the Cover block’s instructions in the placeholder]

The hardest part was having to figure out what part to click on to add the text.

I’m not really sure how I can add [a block at the bottom of the page]

Video 2 (July 10)

Oh, the text is here. I couldn’t even tell. I wish there was an indication. [referring to where to add text in the page]

So it’s kinda like a puzzle. I can move these elements around.

Video 3 (July 17)

I’m afraid you’re using terminology that doesn’t mean that much to me.

I’m going to give up on this. [referring to the Media Library and adding items to gallery]

This isn’t obvious or intuitive at all.

Video 4 (July 24)

Feedback

As with all the prior videos being shared, please leave some feedback! What are some patterns that pop out to you? What successes do these users have in navigating and creating a post? What challenges become evident in their flow?

As a reminder, if you’re interested in helping with usability testing, there’s a number of things you can try:

  • Join the #research channel in slack.
  • You can write a test script that can be usability tested for Gutenberg.
  • Or simply watch the videos and leave some feedback below.

Thanks for watching and contributing anywhere you can.

#gutenberg, #usability-testing

WCEU usability test results: part two

This is the second and final batch of usability tests from WCEU. You can catch up on the first five here.

As you watch through have a think about a few things:

  • What bugs or enhancements could be made from this?
  • What insights do you gain in the way people use Gutenberg?
  • Any ideas come up to make the editing experience even more useful?

Share anything you have as a comment and part two will be along in a few days.

Continue reading

Gutenberg Usability Testing for May 2019

As noted in last month’s post, I’m conducting a usability test every week on userbrain.net for Gutenberg. These tests are a way to keep track of Gutenberg’s progress and improvements. It also helps reveal any additional UX issues that may not have been evident.

This month focused on image and video blocks. It also involved editing content in relation to those blocks like moving them up and down in the post, and adding captions.

Testing Script

Imagine you are on assignment to write an article for a new travel blog. Luckily, they are sending you to your favorite vacation spot! Your instructions are to choose a topic you think will get people as excited as you are about this place. It’s up to you to pick a focus (food, activities, lodging, etc.).

  1. Log in.
  2. Create a new post.
  3. Give your post a title and add one sentence.
  4. Add two images side-by-side.
  5. Add a YouTube video (https://www.youtube.com/watch?v=-PcrLWkxZSk).
  6. Add a caption to the video you added.
  7. Swap one of your previously added images with another image.
  8. Add an image on the left and some text on the right and a paragraph below it.
  9. Move the video to the bottom of the content.
  10. Once you’re done, publish the post.

Videos

Video 1 (May 6, 2019)

Video 2 (May 13, 2019)

Video 3 (May 20, 2019)

Video 4 (May 28, 2019)

Feedback

Please watch the videos and comment on anything you noticed particularly interesting about how these users used Gutenberg. It would be great to call out points of struggle which can be connected to opportunities, or even points of success that can be positive indicators of improvements.

As a reminder, if you’re interested in helping with usability testing, there’s a number of things you can try:

  • Join the #research channel in slack.
  • You can write a test script that can be usability tested for Gutenberg.
  • Or simply watch the videos and leave some feedback below.

Thanks for watching and contributing anywhere you can.

#gutenberg, #usability-testing

Gutenberg Usability Testing at WordCamp Europe

This year, there will be a usability testing table at WordCamp Europe for Gutenberg, similar to the past one at WordCamp US. I’m looking for as many volunteers as I can find to help run tests at WCEU or process the tests remotely after the conference.

Get involved running tests

Tests will run for 30-minute blocks over the course of the WordCamp. To be involved, you must be attending WCEU. You can sign up here.

What do you need to do?

Facilitators will be in charge of the testing time. If you wish to just run tests and not co-ordinate, please sign up as a tester.

Facilitators should ideally have some usability testing experience, but if you’d like to try facilitating regardless, there will be information that will help you run sessions.

Facilitators will:

  • Welcome people interested in testing Gutenberg.
  • Set up testers with the Gutenberg test survey and the Gutenberg testing site, then start the provided screen recording app.
  • After the test is complete, save the test recording and reset everything.
  • Chat with testers about their experiences and their thoughts on Gutenberg, taking notes where possible.

If you are not attending WCEU, there is still a way you can help out: after the event, there will be a post created asking for volunteers to help process the tests.

Hope to see you there!

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!

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