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

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

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 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 5.7.0 rc.1

This release includes

Features

Enhancement

You can find a full list to test against here.

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 WordPressDownload Gutenberg 5.7 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 the new features and also if existing flows work.

You can also see other options for getting set up for testing in the handbook. When testing, use the latest stable release of WordPress (5.1) and the Gutenberg 5.6 plugin (download using the links above). All testing is welcome even if it’s just one or two items!

If you find a new bug, please file it in gutenberg on GitHub. Thank you! Please join us in #core-test on WordPress Slack any time if you have questions about testing!

#5.7, #call-for-testing#gutenberg

Call for Testing: Gutenberg 5.6 rc.1

This release includes:

You can find a full list to test against here.

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 5.6 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 the new features and also if existing flows work.

You can also see other options for getting set up for testing in the handbook. When testing, use the latest stable release of WordPress (5.1) and the Gutenberg 5.6 plugin (download using the links above). All testing is welcome even if it’s just one or two items!

If you find a new bug, please file it in gutenberg on GitHub. Thank you! Please join us in #core-test on WordPress Slack any time if you have questions about testing!

#5.5, #call-for-testing#gutenberg

Call for Testing: Gutenberg 5.5 rc.1

This release includes:

  • Try using a Group block by adding some inner blocks to it and changing the Group block background color.
  • Add vertical alignment support to the Media & Text block.
  • Add the image fill option to the Media & Text block.
  • Lots of bug fixes and enhancements.

You can find a full list to test against here.

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 the new features and also if existing flows work.

You can also see other options for getting set up for testing in the handbook. When testing, use the latest stable release of WordPress (5.1) and the Gutenberg 5.5 plugin (download using the links above). All testing is welcome even if it’s just one or two items!

If you find a new bug, please file it in gutenberg on GitHub. Thank you! Please join us in #core-test on WordPress Slack any time if you have questions about testing!

#5.5, #call-for-testing#gutenberg

Would you like to help test Gutenberg?

We would love to have you! Gutenberg releases are happening every few weeks right now.

To help with general testing after opting in to the “Try Gutenberg” callout in the WordPress 4.9.8 dashboard, please comment here or say hello in #core-test on WordPress Slack.

To help with pre-release testing, or regression testing, first get a testing environment setup.

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

Anyone can jump in to help with issues labeled Needs Testing and if you are a developer then issues labeled Needs Technical Feedback would be a great place to lend a hand. See the bug testing guidelines in the handbook for some tips.

If you want to help and aren’t sure where to start, just ask!

#editor

Help us Analyse the WCUS Gutenberg Usability Videos!

Huge thanks to everyone who participated in usability testing at WCUS. Our next step is to analyze the video footage – and we need your help!

The rest of this post tells you how you can help us with the analysis, even if you are new to usability testing and have never done this before.

If you have any questions comment below or better yet ping us in #core-flow on WordPress Slack.

How to analyze video footage:

  1. Go to the Volunteer Reviewers tab to fill out your name, Slack username and your WordPress.org username.
  2. Go to the Survey Results tab to assign yourself at least 5 videos to review. Enter your name in column B (or column D if column B is NOT empty) of the videos you are reviewing.
  3. Go to the session tab using the ID link listed in column A of the Survey Results tab.
  4. Review the tester’s survey results before watching the video.
  5. Follow the video link to watch the session and enter the following information in the highlighted cells:
  • Start time – when the tester started using Gutenberg.
  • End time – when the tester completed the task in Gutenberg.
  • Summarize the participant’s WordPress experience, if they mentioned it. (Some participants were asked or may have mentioned it during their session.)
  • Take notes about the user experience in the note section below. Include the timestamp from the video for the note, select note type (Bug, Pain point, or Insight) and your name with each note.
  1. Return to the Volunteer Reviewers tab to summarize the sessions in column E. Include any notable or/and recurring themes. If you feel a video should be reviewed by the Gutenberg team, specify this in column F.

For your reference, these are the two sample posts users were asked to replicate using Gutenberg: Test 1, Test 2.

Tips on Reviewing:

  • When taking notes on the session, please be sure to keep your feedback separate from the participant feedback. Notes on the individual session tabs should be from the participant. If you have suggestions or conclusions of your own, keep those on the reviewer’s tab, and be sure to flag any videos you think worthwhile for additional review.
  • Watch for and note any instances where user confuses functionality, i.e. looks for caption when should be attempting to add a block quote, etc. or moments of delight, was there anything they mentioned that they liked?
  • Note whether the participant succeed in completing the task or if they gave up. Try to note where or why they stopped.
  • In attempting to complete the task, does the participant pause for any length of time? Do they hover the mouse or appear to randomly click around? Does the participant get “lost”? Try to note what they were attempting to find or trying to do during this time.
  • Watch for visual cues from the participant like a furrowed brow of concentration, or audible cues like “hmmm…”? If these occur, note what the participant was trying to do at the time. If they solved it, are you able to note how?
  • If available, watch through the participant completing the Part 3 end survey. Do their responses provide any additional insight on pain points they experienced during the task? Sometimes participants will provide additional explanation of why they seemed to struggle. Is there anything they say but don’t type into the form?

Special thanks to @betsela, @fuyuko, @annaharrison, and @lynneux for developing and refining these plans.

Gutenberg usability testing meeting three

Last week we had a usability meeting. The meeting time wasn’t good for everyone, so let’s change the time this week.

When? Tuesday 31st October 19:00 UTC.
Where? wordpress.org Slack #core-flow: the testing channel.
Who should come? Anyone interested in helping test Gutenberg, all skill levels welcome.

Last week we talked about plans for testing. We will continue that conversation this week.

#gutenberg