Lesson #14 - Testing continues
course taught in classroom PM and Programmers attend [an error occurred while processing this directive]


Everyone is busy testing each others sites and presenting the site to the clients. Hopefully the majority of the work is done, unfortunately the details will get you every time. At this point in the project, I often print out the website as it exists and make corrections and notes on paper. I often miss things on the screen that stand out in print. I also develop long lists of things to do. The longer the list - the more satisfaction you derive from crossing things off.

Testing with Typical Users

  1. Recruit test-run participants (3-5) who are similar to your intended user. Refer back to the "target market" description. The important thing here is that the test user should, as much as possible, be like your "real" user so you get the most accurate information.

  2. Have the test-run participants use the web site. It is not necessary to bring the whole group together at once. Depending on your site, you may get better information if only one or two people participate at a time.

  3. Observe the test-run participants as they use your web site. The important thing here is to try not to interfere. In order to get accurate information, you must not jump in to "help" as soon as you spot an apparent problem. Of course, if participants really get stuck, you do want to work with them so they can continue to test your product.

  4. Make notes. Your notes should include information about where any problems occurred, under what circumstances, and how the person attempted to resolve or actually did resolve the problem. You should include any participant reactions, both positive and negative, which you observe. Your notes should include information such as "Opening Screen - participants clicked on the logo make logo appear less like a button or 2 users seemed bored waiting for the graphics to load on the products page

  5. Ask questions. Your questions should help clarify why people are doing what they're doing (i.e., When you got to the opening screen what did you think your choices were ). Your questions should also help you make changes (i.e., What would you suggest we do to make this screen, page, web site, etc. less confusing?).

Other techniques you may want to try include

  1. Have the test-run participants make notes as they use your web site. This is a good way for the test-run participants to capture things as they happen. You will likely get confirmation of problems you observed as well as some on-the-spot thinking which you cannot observe very easily. This is also a useful time to collect information if you are unable to directly observe the test-run participants.

  2. Have the test-run participants complete a survey. This is a more systematic way to collect the information you are after. All test-run participants answer the same questions, and you can quickly see any trends that develop. Like the test-run participant notes, a survey is also a good way to get information if you are unable to observe the participants yourself.

  3. Direct observation of the test-run participants is probably the best way to find out where any "problems" exist in your product. However, any or all of the other methods will provide you with valuable information on whether your web site really does what you intended it to do.

  4. Conduct interviews/focus group after the test-run. This is not expected in this class and is most often done in industry when time and $ are more plentiful. Individual interviews allow you to obtain more detailed information from each person interviewed. Focus groups also give you detailed information as the participants use each other's comments and thoughts to stimulate and elaborate on their own comments and thoughts.

Testing under various Hardware and Software configurations
The conditions your site should be tested under includes:
  1. browsers (Netscape and IE) current version and one version back
  2. platforms (Windows 98 and Mac OS9)
  3. screen sizes (15"- 21")
  4. net connection (slow modem, DSL, cable modem, T1)
  5. screen colors (256, thousands, millions
  6. use with adaptive devices found in Hi Tech Center (see below)

I need you to view your web site at the High-Tech Center which contains computers which have adaptive devices for students with disabilities. Call Richard at 527-4890 and set up an appointment for 15-30 minutes sometime within the next 2 weeks. You will be allowed to view your web site using the equipment and determine how the site looks to the disabled

Take note of any problems including:

  1. color distortion (is it major or can you live with it?)
  2. graphics or text that does not fit on the screen
  3. dramatic changes in layout
  4. site cannot be navigated at the high tech center
  5. length of time the site takes to load on a slow modem


Content for these teaching materials were developed by Linda Hemenway. If you have questions or comments on the material I can be contacted through
lhemenway@santarosa.edu
(707) 527-4855

Web site design by Jessica Hirsch - jessicahirsch@email.msn.com

Funding for these notes provided by Project FIVE and Project PICTS supervised by Doug Garrison - Dean of the Petaluma Center.

This course is a core requirement for several Web Development Certificates. Learn more at the Web Certification site.

The CIS Department offers courses in the following areas: computer basics, applications, graphics, web development, productivity, networking and programming. Visit the CIS Web site.
 
lessons | homework | syllabus | grades | links | examples | home

    1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 - 12 - 13 - 14 - 15 - 16 - 17 - 18