Tag Archives: testing

Usability Testing: Why Aren’t We Doing It?

I was recently selected to speak at the SPSEMEA SharePoint Saturday. For the talk I wanted to talk about the often forgotten art of usability testing on SharePoint projects. All of the content is generic and applicable enough that you don’t have to be implementing SharePoint to get something from this presentation. The content is made to be applicable to any type of application implementation.

Presentation

I made a video that was my actual presentation including going over all of the slides and analysis on the usability test. The presentation runs slightly over 50 minutes. You can also download the slides from the talk as well.

Usability Test

If you want to watch and think through the usability test in its entirety without my commentary you can view it through the UserTesting.com site.

View Usability Test

Resources Mentioned in Presentation

Here are links to the various sites and applications I mention in the slides.

Using hMailServer with SharePoint

When testing and/or developing with SharePoint it is helpful to test and use e-mail functionality. You might be working on a workflow or want to demonstrate alerts to potential stakeholders, and it would be nice to do this in your testing environment. The problem is that traditionally Exchange is used for this activity, and when you’re in a testing environment adding the bloat of Exchange to an environment that is already nearly maxed isn’t an option. Enter hMailServer.

hMailServer is a full featured e-mail server, but we’re just going to use it for e-mail relay (SMTP) (I found a post with supposedly a VB script for specifying the drop folder for incoming e-mail but haven’t worked with it). This is also only a good idea for testing purposes. While I don’t see why hMailServer cannot be used for deployments (albeit small ones) it still isn’t advisable. Most likely if you’re implementing SharePoint in your enterprise then you’re already drinking the Exchange juice so just use that.

Installing and Configuring hMailServer

1. First you’ll want to download hMailServer.

2. Start the install.

3. Move through the prompts, but choose full installation when asked.

4. It will then bring you to a screen asking you about the database to use. Since we’re already running SQL Server for SharePoint let’s use that so select “External Database Engine.” (Clicking the images will magnify them.)

Specify Database Engine

Specify Database Engine

5. After finishing the install it will open up a database wizard. The first option we’re giving is the database instance. Select the option to  create a new hMailServer database.

Create Database

Create Database

6. Then it will ask for information to connect to your database instance. The database server address is most likely your computer name (contoso for me), and then choose whatever you want to call the database. Lastly, choose the Windows authentication option for authentication mechanism (most likely the account you’re using has the dbowner role on SQL Server but if not add it).

Server Connection Info

Server Connection Info

7. Then you will be prompted to select the service instance. Select the SQL Server (MSSQLSERVER) service.

Service Instance Selection

Service Instance Selection

8. Move through the next screens (it will provision the database), and then lastly you will be prompted to specify a password for the admin account. Add one and finish the wizard.

9. Next it will open the hMailServer administrative interface. Login and expand the following nodes: Settings — Advanced — IP Ranges. Highlight My computer. Then specify 0.0.0.0 as the Lower IP and 255.255.255.255 as the Upper IP.

IP Relay Configuration

IP Relay Configuration

10. Now click on Domain in the navigation panel. Here you’ll add a domain. I chose my computer name (with a .com suffix), and then click advanced and specify a catch-all e-mail address. You can then exit the hMailServer administration interface.

11. Next open Central Administration. We will now specify the outgoing e-mail settings by clicking on the System Settings header on the splash page and then choosing “Configure outgoing e-mail settings.”

12.For the “Outbound SMTP server” put in your computer name, and I put in my catch-all e-mail address for the “From address” and “Reply-to address.” Save your change.

Central Admin E-mail Settings

Central Admin E-mail Settings

13. Lastly, I tested it by adding a user to a site with an e-mail specified in AD, and it worked!

E-mail Success!

E-mail Success!

Economical Usability Testing

Usability testing is often overlooked to the peril of both the developer and the consumer. I was convicted reading Steve Krug’s book on usability to go ahead with testing even if it’s small and cheap. In doing this for the recent design of this site I wanted to share how I did usability testing for all of $60.

Feedback Form

The first thing I did was create a form in Wufoo, a powerful form building application, to receive feedback. I made it simple and short (I had to keep it to 10 fields in the free version). I made an announcement on my personal blog offering a small gift certificate to Amazon for the most in-depth results. I got so many good ones that I decided to give out 4 $10 gift certificates instead of the two I mentioned in the blog post. I got some great feedback from age groups varying from teenager to baby-boomer, male and female, and different income families. I even had a scale from very technical to a casual user of the Internet. Here are some of the comments I received (a sample of the results).

What is your impression of the home page, and where do you want to go first?

  • It’s bright and I am having some trouble with the lack of contrast…”
  • The home page makes a strong impression. The design itself is simple, but effective.”
  • I went first to services to see if you could back up the claims in the home page text, then to portfolio to check out your abilities.”
  • It’s very green. Probably too green. In the least I would reverse the greens…”

Is the text easy to read?

  • Too small.…I like bigger type and bolder.”
  • The white text in the menu with the dark green background is difficult to read.”
  • Change the text size in the browser window, and it skews things…”

Final Comments

  • The terminology is confusing because I am an accountant and not a web programmer.”
  • When searching, I wasn’t sure if it would search page content and articles, or only articles.”
  • Possibly adding a snippet of the page in the search results (rather than just a link to the page) would make it more helpful.”
  • I don’t like how when I’m looking at more pages of articles, I’m still at the home page. It seems like when I click on “Next” it should open up to something bigger.”

Video Taped Usability Session

I also paid $20 to have someone sit down and answer questions related to the site. It came from a site called User Testing.com. I appreciated the results, and I thought I would share the results with you. You can also gauge the differences between the old and new versions.

Instead of embedding the media, please view the usability test results in a new window.

Changes Made 

It doesn’t mean much unless I actually make changes as a result of this effort. Here are some changes I made in response.

  • Removed the pagination on the front page to take the user to an archives page.
  • Swapped the greens to make the softer one more prominent.
  • Add excerpts to the search/archives page to describe article content.
  • Made clear on the search page what was actually search (both articles and pages).
  • Explained what the “*” meant on the contact page (which I mistakenly thought was not needed).
  • Changed the overflow on the main page to scroll when text size was increased so as to not throw off the layout.
  • Changed the terminology from “Goodies” to “Downloads”.
  • Changed the color on input forms from a light gray to black for more contrast.
  • Removed confusing “blog categories” drop down from pages.
  • Removed technical jargon from the “Services” page, and trimmed the “About” page (and I still need to do more).

Conclusion

After going through this process I was grateful for the feedback I received, and I’m happy with the changes I made. I didn’t have to make every suggested change, and I filtered that by whether I felt the user fit into the demographic of people who would visit my site.

It is gratifying to make an appliacation this is usable, and it’s much easier to receive the constructive criticism from real users and not an executive telling me what my users want. I would highly suggest that a similar approach be taken early and often in the development to ensure that your users are satisfied with their experience.