Call for testing: Gutenberg

Gutenberg is now in beta, with that comes a new opportunity for testing.

There is now a testing page dedicated to Gutenberg, you can find it right here. There are currently 2 types of testing being looked for, each has a central feedback form.

Looking for other ways to give feedback? You can also write a blog post (let the editor team know about that in Slack #core-editor) or add an issue to the GitHub repository.

Your feedback and testing is really important at this stage of Gutenberg, it really does matter and help make this as good as it can be.

+make.wordpress.org/core +make.wordpress.org/design

#needs-testing

Additional CSS

#css

Theme editing

#editing

Plugin editing

#editing

A new call for testing…

A new call for testing is out for the prototype editor. It looks neat! If you’d like to help test, remember that it’s in very early prototype stages so functionality is limited and they’ve asked for help with the following (other functions haven’t been built yet):

  1. Add a new paragraph.
  2. Add an image.

Written response:

  1. Is it clear what each section does?
  2. How do the flows for adding paragraphs and images feel overall?

Post testing notes on the thread at https://make.wordpress.org/design/2017/02/09/initial-gutenberg-prototype-editor-testing/

Report bugs (search first!) at https://github.com/WordPress/gutenberg/issues

#needs-testing

X-post: Share a walkthrough of setting up a WordPress site

X-post from +make.wordpress.org/design: Share a walkthrough of setting up a WordPress site

WordCamp Contributor Day: Workshop Findings

December 4, 2016

WordCamp Contributor Day: Workshop Findings

BACKGROUND

Goals

This test allowed Flow Patrol to 1) observe sign-up and log-in flow, as well as 2) gauge user experience of creating an entirely new site solely through the WordPress Mobile App version 6.2 on Android 5.1.

Tester

The tester has experience using WordPress, but has procrastinated making a blog for a long time. He has used WordPress for other things, commercial sites for example, but has never made a blog because he finds it difficult to get into writing. The tester is a recent Android user, who is new to using smartphones in general, and often expressed that he dislikes prolonged typing on mobile devices.

 

OBSERVATIONS

Sign-up

Since the tester has trouble typing on mobile devices and was self-conscious about making mistakes, he began looking for a “show password” button as he navigated the sign-up page. He commented that it needs to be more visible and thinks perhaps the image of a crossed-out eye is too abstract for some users.

The tester found that an account already existed under the name he wanted and figured it was his old one. However, he was required to back out of the sign-up page before navigating to the log-in page to try entering it. He commented that it would be nice to simply be taken to the log-in page for the account once WP discovered it, or at least to be prompted to try to log into that site.

The tester clicked on “forgot password” and was redirected to the browser version of WPs’ sign in page, which caused some confusion. He said that he expected to leave the app to retrieve an email confirmation from his email inbox, but he didn’t understand why he was taken outside of the app to reset the password. He said that changing platforms like this takes a person out of their work-flow. He admitted that this left him with a bad impression, explaining that if WordPress can claim to power over a fourth of the Internet, he expects that it “should have this figured out by now.”

 

Log-in/Log-out

Done with sign-up, the tester tried to log in with what was believed to be his “username”, but could not get in because it turned out that he was using his “public display name.” In the site navigation screen, the “public display name” is emphasized – it’s a darker, larger font and above “username.” Log-in using email address was successful.

The tester attempted to log out to figure out which name was to be used to log in. A “log-out” button was difficult to find, because it was expressed as “disconnect.” The tester expressed fear at the confirmation prompt, which seemed like a warning about permanent deletion of accounts, sites etc. He suggested that it simply be called, “log-out.” Only after two successful log-ins did tester realize the difference between and significance of “username” and “public display name.”

 

Site Creation

Once logged in again, the user saw past sites displayed on the opening screen. The tester explored other parts of the site looking for a “create new site” button. He openly questioned where he should go, even exploring “account settings.” The tester expressed that he felt stupid and surprised that it was difficult for him to find. After prompting from the interviewer that he search back at the “show sites” screen where he started, he found a plus sign which turned out to be what he was looking for all along.

When asked where he expected it to be, the tester explained that maybe front and center was not appropriate because he already had sites and doesn’t create them all the time. Still, he found “show sites” to be misleading because it implies that it would take him to view existing sites only. He only found it when looking for it intently and with extra help. The tester suggested that the plus sign makes sense, but could be emphasized by making it a brighter color.

 

First Post

The tester was intent on creating a quick post just to see how it would look. He successfully created a simple post with a title and a sentence in the body. When he then viewed the post, it opened up in the app itself, which he liked. He then checked the post on the mobile browser and was satisfied with the way everything looked. The end result matched his expectation.

 

VISUAL RECORD

A visual record of this test does not exist. Subsequent testing will hopefully provide such data.

 

CONCLUSIONS

At the end of the test, the tester offered this feedback:

  • Publishing was a great experience and everything went as expected.
  • “Switch sites” proved to be misleading and he might not have looked there without guidance.
  • Logging in was frustrating and “could have been done better.” The tester was not a strong typist, and was made to do it several times. He admitted that if it wasn’t for the sake of test completion, he would have put the app down and “done it later,” perhaps not revisiting it for some time.
  • After the test, the tester admitted that he would likely never pick up the app again anyway. Writing is not something the tester would do on the go; he prefers instead, a laptop or desktop to work from.
  • The tester would instead want the app for notifications that would help him keep up to date with happenings on his site. He said that an ideal app would allow him to make quick corrections, approve work submitted by other writers on a shared blog, track business/e-commerce information, and generally keep track of his site when away from keyboard.

Customizer: Browse, Install, Preview Themes on Mobile

I tested the patch proposed on #37661 on Windows Phone 10 with the Edge browser. Here’s a visual record of that experience:

The biggest potential fixes I found were to show a loading indicator in the filters (next to the theme count button in the header?) when a new filter is loading, and to scroll the themes container to the top whenever a new section is opened or a search/filter is changed (which should be happening, but isn’t).

I should also note that since it is impossible to reorder images in galleries with Chrome on laptops that support touch, see #31652, I had to go to the text editor to fix one that jumped out of order when creating this post.

#customize, #customizer, #edge, #phone, #shiny-updates, #visual-record, #windows-phone

Better Dogfooding Tips

This was originally written by @karmatosed. I’ve adapted it for WordPress.org.


Dogfooding is a great way we can use WordPress and test our features. By testing WordPress ourselves, we get to unearth all manner of bugs, issues and fun things. Try setting up a new site from scratch, especially thinking about specific use-cases like a new photoblog, or a company website.

I thought it would be great to come up with some tips for so new folks doing dogfooding can have a resource to start with. So, without further ado here’s just that!

Format

How you present the post really helps for people to read and also how we can use later on. A rough format for reporting your observations via video that works is:

  • Title: Make sure your title has the word “dogfooding” in it somewhere, so it’s easy to scan. Also include what feature you’re testing in title. ex: Dogfooding: Theme Setup
  • Use the more tag to shorten posts. It helps keep the p2 streamlined so it’s easier to scan.
  • Talk about your perspective as a user, and what you’re trying to accomplish.
  • Embed the video in your post.
  • Under the video, pull out any key points at minute marks. ex: 01:00: here’s where I spent a whole minute trying to search for directory themes from my installed screen. Keep this list short; don’t worry about pulling everything out, as if this is long, people will be less likely to read. Just make sure to list the biggest finds.
  • After that, it’s often useful to chop up the video (if it’s very long) and pull out significant clips. Making clips like this is useful for bug reporting and summaries. Clips can go after or next to minute marks, and also next to bugs for easier visual reference. Just consider that not everyone will want to watch your entire video. 🙂
  • Bugs: List out any bugs you found while testing. You can even do a fun thing by putting the bug emoji at end to make them stand out: 🐛
  • Summary: Summarize the main issues and conclusions you found from testing. ex: I stumbled a lot with the theme installation process because… If we did x or y it might improve this feature…
  • Tags: Tag it #dogfooding and anything else relevant.

Here’s what the above would look like laid out:

  1. Dogfooding: Feature You’re Testing
  2. As a user, I’m trying to accomplish x
  3. Video embed
  4. 1:00: something amazing, 2:00: something else amazing
  5. Significant clips
  6. Bugs 🐛
  7. Summary
  8. #dogfooding

Reporting

If you see a bug, report a bug. It’s important we follow through on the bugs and don’t just leave them on this p2.

The same goes for things you think are issues, or even enhancements. Sometimes you may think of something awesome nobody else has thought of before, and it could become something that changes the life of our users. Pretty cool right? That’s why it’s very important to report on trac.

Enjoy and please dogfood 🐶


 

This has also been x-posted to make/design.

Shiny Updates User Testing – update-core.php

Originally by @mapk posted on Slack

The first user test on update-core.php:

 

Notes:

1. Great confirmation to the recent changes we’ve done.
2. She provides some alternate ideas on how to order the updates in the list: by importance, or by update release date.
3. One of my concerns was whether or not it was easy to identify the different types of updates now that they’re all included in the same list. She was able to find a “plugin” to update just fine once she realized they weren’t all plugins.

Also:

“It was a super easy update process”
“if this is the way it is, you should keep it and never gonna think about changing that”

#shiny-updates, #upgrade-install