iOS app site deletion, iPhone 6+

Testing site deletion with build 6.0.0.20160217ebd5529 on an iPhone 6+.

Some screenshots:

Here is the site after deletion:

IMG_8046

Notes:

  • On the delete confirmation screen, I didn’t read any of the text on my first time through. I saw a text input in a delete confirmation and assumed my password was needed. I pasted my password and noticed that it was shown in the clear. Hmm. I noticed also that the delete site button was still disabled.  Hmmm. Finally, I read the text and saw that I was being ask to perform a different kind of AYS gymnastic, typing in the site name.
  • Otherwise, the process was straightforward and worked.
  • Not pictured in the screencast: To test this I created a new site. If you are scrolled down the site list when adding a new site, you won’t see any acknowledgment that the new site was created successfully. You must scroll up to see the new site at the top of the list.

 

#app, #ios, #phablet, #safari, #sites

Profile: Profile editing, WP iOS Beta, iPhone 6+

Testing profile editing with iOSiOS The operating system used on iPhones and iPads. app betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. 6.0.0.20160208. Looks good. My only note is making About Me a textarea. Horizontally scrolling through a paragraph of text in a one line input field is awkward.

#app, #beta, #ios, #phablet, #profile

Joining the Android Beta Program

I had difficulties finding out how to join the Android betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. program. make/mobile contains no mentions of beta testing other than links to the G+ community page in call for testing posts. I never use G+. After crossing the G+ log in threshold and the community join request threshold, I required several minutes of clicking around to find the beta testing instructions. Exasperated by the absurd experience, I copied the instructions to a new testing section of the handbook to move them out from behind the G+ sign in and make them somewhat  discoverable.

Here’s a step-by-step visual record for joining the Android app beta program starting from a link on a call for testing post on make/mobile.

Testing patches with VVV on Mac OS

Install Vagrant

Download Vagrant from https://www.vagrantup.com/downloads.html.

Click MAC OS X.

Screen Shot 2016-01-28 at 9.53.03 AM

Click vagrant_1.8.1.dmg.

Screen Shot 2016-01-28 at 9.54.54 AM

Click Vagrant.pkg

Screen Shot 2016-01-28 at 9.56.35 AM

Click Continue.

Screen Shot 2016-01-28 at 9.57.36 AM

Click Install.

Screen Shot 2016-01-28 at 9.58.17 AM

Enter password and click Install Software.

Screen Shot 2016-01-28 at 9.59.01 AM

Click Close.

Screen Shot 2016-01-28 at 9.59.14 AM

Install Virtualbox

Download VirtualBox from https://www.virtualbox.org/wiki/Downloads.

Click VirtualBox 5.0.14 for OS X hosts amd64.

Screen Shot 2016-01-28 at 10.02.22 AM

Click VirtualBox*.dmg

Screen Shot 2016-01-28 at 10.03.55 AM

Double click VirtualBox.pkg.

Screen Shot 2016-01-28 at 10.05.04 AM

Click Continue.

Screen Shot 2016-01-28 at 10.05.45 AM

Click Continue again.

Screen Shot 2016-01-28 at 10.06.29 AM

Click Install.

Screen Shot 2016-01-28 at 10.06.58 AM

Enter password and click Install Software.

Screen Shot 2016-01-28 at 10.07.27 AM

Click Close.

Screen Shot 2016-01-28 at 10.08.08 AM

Initialize Vagrant

Launch the Terminal app. One way of doing this is to open Spotlight with ⌘ + space and then type Terminal.

Screen Shot 2016-01-28 at 10.18.17 AM

Enter sudo vagrant plugin install vagrant-hostsupdater

Screen Shot 2016-01-28 at 10.25.29 AM

Type your password and hit Enter.

Screen Shot 2016-01-28 at 10.25.34 AM

Success.

Screen Shot 2016-01-28 at 10.25.55 AM

Enter sudo vagrant plugin install vagrant-triggers

Screen Shot 2016-01-28 at 10.28.55 AM

Success.

Screen Shot 2016-01-28 at 10.29.19 AM

Install GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/.

https://git-scm.com/download/mac

Todo: Step-by-step screenshots

Install VVV

Create a directory for your VVV sandboxes. I call mine Sandbox.

Enter mkdir ~/Sandbox

Screen Shot 2016-01-28 at 10.32.03 AM

Enter cd ~/Sandbox

Screen Shot 2016-01-28 at 10.34.37 AM

Clone VVV by entering git clone git://github.com/Varying-Vagrant-Vagrants/VVV.git vagrant-local

Screen Shot 2016-01-28 at 10.36.12 AM

Success.

Screen Shot 2016-01-28 at 10.36.34 AM

Enter cd vagrant-local

Screen Shot 2016-01-28 at 10.37.59 AM

Enter vagrant up

Screen Shot 2016-01-28 at 10.43.21 AM

Enter your password when prompted.

Screen Shot 2016-01-28 at 10.44.03 AM

This takes a long while as there is much to download. Refresh your beverage and come back in about an hour.

Success.

Screen Shot 2016-01-28 at 10.44.12 AM

Enter vagrant ssh

Screen Shot 2016-02-08 at 8.09.31 AM

Success.

Screen Shot 2016-02-08 at 8.09.45 AM

Enter cd /srv/www/wordpress-develop/

Screen Shot 2016-02-08 at 8.14.23 AM

Enter sudo npm install

Screen Shot 2016-02-08 at 8.14.38 AM

Success.

Screen Shot 2016-02-08 at 8.14.59 AM

Enter sudo npm install -g grunt-cli

Screen Shot 2016-02-08 at 8.16.44 AM

Success.

Screen Shot 2016-02-08 at 8.16.55 AM

Enter grunt build

Screen Shot 2016-02-08 at 8.20.14 AM

Success.

Screen Shot 2016-02-08 at 8.20.08 AM

These sites are now available via your browser.

Apply a patch

Before applying a patch, make sure VVV is running and ready. Issue the following commands in a new terminal window.


cd ~/Sandbox/vagrant-local/
vagrant up
vagrant ssh
cd /srv/www/wordpress-develop/
grunt watch &
svn up

Now you’re ready to patch. Find a ticket with patches. This examples uses #11863.

Enter grunt patch:11863

Screen Shot 2016-02-08 at 8.38.49 AM

Using the arrow keys, select the desired patch. You’ll almost always want the latest one, which is pre-selected.

Screen Shot 2016-02-08 at 8.39.27 AM

With the desired patch selected, hit enter.

Screen Shot 2016-02-08 at 8.40.58 AM

If the patch did not apply cleanly, drop a comment on the ticket nothing that the patch does not apply cleanly and needs to be refreshed.

The patch is ready to test. Visit http://src.wordpress-develop.dev/ and log in with the username “admin” and password “password”.

When done testing, remove the patch using svn revert.

Enter svn revert -R .

Screen Shot 2016-02-08 at 8.49.14 AM

Successful revert.

Screen Shot 2016-02-08 at 8.50.19 AM

Comment on the ticket with testing notes and testing steps. If the patch alters user interface, upload screenshots of the patch in action.

Resources

  • https://make.wordpress.org/core/handbook/testing/patch/
  • https://make.wordpress.org/core/handbook/tutorials/installing-a-local-server/installing-vvv/
  • https://make.wordpress.org/core/2015/03/16/mobile-patch-testing-with-vvv-and-xip-io/
  • https://github.com/Varying-Vagrant-Vagrants/VVV
  • https://www.vagrantup.com/downloads.html
  • https://www.vagrantup.com/docs/getting-started/
  • https://www.virtualbox.org/wiki/Downloads
  • https://git-scm.com/download/mac

 

Shiny Updates User Testing Continued

After implementing a lot of the current revisionsRevisions The WordPress revisions system stores a record of each saved draft or published update. The revision system allows you to see what changes were made in each revision by dragging a slider (or using the Next/Previous buttons). The display indicates what has changed in each revision. for the feature pluginFeature Plugin A plugin that was created with the intention of eventually being proposed for inclusion in WordPress Core. See Features as Plugins., Shiny Updates, we thought to do more user testing. I created a tests for the plugins process and the themes process on wp-admin. These are the results.

PLUGINS PROCESS

Testing: Installation, Activation, Updating, and Deleting of plugins

I expected to learn if there were any drawbacks on the current version of Shiny Updates, and observe any benefits to the process as well.

Tasks

  1. Login to site
  2. Search for a new 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 install it
  3. Activate the plugin
  4. Find a plugin that needs updating and update it
  5. Delete the plugin previously installed

Takeaways:

  • 0.55 – Initially the little circle notification in the sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. next to “Plugins” is orange, but once the user clicks in to ‘Add New’ it changes to be a blue circle. I don’t understand why here and this probably resides outside the Shiny Updates plugin anyways.
  • 1.30 – User is unsure how to ‘activate’ a plugin from the ‘Add New’ screen.
  • 2.16 – The green success notification still says “Updating…” instead of “Updated” or “Updated Successfully”
  • 2.41 – After deleting a plugin, the user is taken to another screen that asks if they want to delete all the files. Are we trying to get away from these screens and keep everything inline with the plugin? If so, can we move away from this screen and just present a msg inline instead?

 

THEMES PROCESS

Testing: Installation, Activation, Updating, and Deleting of themes

I expected to learn similar issues or benefits on the current version of Shiny Updates.

Tasks

  1. Login to site
  2. Search for a new theme and install it
  3. Activate the new theme
  4. Find a theme that needs an update and update it
  5. Delete the theme previously installed

Takeaways:

  • 3:18 – Took the user a while to figure out which themes needed updating. This is probably because the notification blends in too easily with the theme thumbnail.
  • 5:22 – It’s not clear how to delete a theme that is active. Maybe there could be a disabled ‘Delete’ button in the modal with a note that says you can only delete themes that aren’t active.
  • 6:54 – After reading the help documentation, the user expects to see a ‘Delete’ button in the modal but doesn’t see it.

Editor: Inline link editor, iPhone 6+

Testing #33301 on an iPhone 6+. 4.5-alpha-36414

#33301, #4-5, #alpha, #inline-link-toolbar, #inline-toolbar, #ios, #phablet

Shiny Updates User Testing

We wanted to get some user research around the Shiny Updates 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 the plugin process in general).

The first tests were done with basic tasks like installing, activating, and deleting plugins. These were without the Shiny Update plugin installed. I also had the user answer a few questions after the tasks as well.

User 1

Questions:

  1. How often do you visit the Plugin page on your own WordPress website?Rarely. I used WordPress.comWordPress.com An online implementation of WordPress code that lets you immediately access a new WordPress environment to publish your content. WordPress.com is a private company owned by Automattic that hosts the largest multisite in the world. This is arguably the best place to start blogging if you have never touched WordPress before. https://wordpress.com/ over a year ago, but had extensive experience with the product.
  2. How many plugins do you typically have installed on your WordPress sites?I would estimate 5-10 plugins.
  3. Is it easy to see which plugins you have installed and to see the status of those plugins?Yes.
  4. Is there anything you’d like to change with the Plugins process?I personally thought it was very easy to use. Any wordpress user would have an easy time using it.

 


 

User 2

Questions:

  1. How often do you visit the Plugin page on your own WordPress website?Everytime I am working on my sites.
  2. How many plugins do you typically have installed on your WordPress sites?2 or 3
  3. Is it easy to see which plugins you have installed and to see the status of those plugins?Yes
  4. Is there anything you’d like to change with the Plugins process?No

 

The next test involved installing Shiny Updates. I really bombed here in the wording of my questions and basically confused the user which lead to uncompleted tasks, but this is a good jump off point. I learned a lot about the differences in the processes myself. 🙂 I’ll document these differences soon.  I’m currently refining the test to help improve the task flowFlow Flow is the path of screens and interactions taken to accomplish a task. It’s an experience vector. Flow is also a feeling. It’s being unselfconscious and in the zone. Flow is what happens when difficulties are removed and you are freed to pursue an activity without forming intentions. You just do it.

Flow is the actual user experience, in many ways. If you like, you can think of flow as a really comprehensive set of user stories. When you think about user flow, you’re thinking about exactly how a user will perform the tasks allowed by your product.Flow and Context
.

User 1 (of next test)

Questions:

  1. How often do you visit the Plugin page on your own WordPress website?I have never visited the Plugin page before. I am familiar with Plugins but have never added them to my WordPress site before this exercise.
  2. How many plugins do you typically have installed on your WordPress sites?I only have any plugins that are automatically installed on my WordPress site. I have never installed any additional plugins.
  3. Is it easy to see which plugins you have installed and to see the status of those plugins?Yes, very easy. The list format is easy to see and read; I like that the status of the plugin is stated directly below the name. It makes it quick and easy to visually know what is installed and activated/deactivated on the site.
  4. Is there anything you’d like to change with the Plugins process?My only suggested change would be to include all of the options offered on the drop down “Bulk Actions” menu directly below the names of each added Plugin. This might make the process of making changes a bit quicker and easier for users. Also. the name Bulk Actions makes it sound as though that is only to be used if making changes to multiple plugins so it may be a bit misleading for users who are attempting to make changes to only one plugin at a time.

 

 

Some takeaways:

  • Doing away with the ‘bleak screen of sadness’ is a great start. That screen tended to cause confusion and required a full read to understand what was happening on that page.
  • The bulk update dropdown and button seem to get a lot of attention even though the user may only be targeting one plugin at a time. This could be due to the fact that that is the primary button in the most relevant place which might misguide them. Users also are not necessarily selecting a plugin before clicking the ‘apply’ button which doesn’t return any useful feedback.

I’ll be modifying the next test and sharing the results shortly.

#shiny-updates, #user-research, #user-testing, #ux

2015 Contributor Survey

Hi flowFlow Flow is the path of screens and interactions taken to accomplish a task. It’s an experience vector. Flow is also a feeling. It’s being unselfconscious and in the zone. Flow is what happens when difficulties are removed and you are freed to pursue an activity without forming intentions. You just do it.

Flow is the actual user experience, in many ways. If you like, you can think of flow as a really comprehensive set of user stories. When you think about user flow, you’re thinking about exactly how a user will perform the tasks allowed by your product.Flow and Context
folks! Thanks for all your hard work and contributions in 2015. Could you contribute few more minutes to fill in the 2015 contributor survey? It will help us establish some baselines around the contributor experience so that we can see how things change over time.

**This is being posted to all the Make teams, so if you subscribe to a bunch of p2s and keep seeing this post, know that you only need to fill the survey in once, not once per team.**

The survey is anonymous (so you can be extra honest), all questions are optional (so you can skip any that you don’t want to answer), and we’ll post some aggregate results by the end of January. It took testers 5-10 minutes to complete on average (depends how much you have to say), so I bet you could knock it out right after you read this post! 🙂

There are two sections of the survey. The first has questions about team involvement, recognition, and event involvement, and is pretty much what you’d expect from an annual survey (which teams did you contribute to, how happy are you as a contributor, etc).

The second section is about demographics so we can take a stab at assessing how diverse our contributor base is. All questions are optional, but the more information we have the better we can figure out what we need to improve. If there’s some information you’d rather not identify, that’s okay, but please do not provide false information or use the form to make jokes — just skip those questions.

The survey will be open until January 15, 2016. Whether you have 5 minutes now, or 10 over lunch (or whenever), please take the 2015 contributor survey. Thanks!

#annual-survey, #contributors

.org: 4.4 release announcement on an iPhone 6+

Many will come upon the release announcement while browsing Twitter or Facebook on a phone. Here’s the view.

image image

 

#org, #ios, #phablet, #responsive, #wordpress-org