Tag Archive: Web testing


So now that testing is done and submitted last week, more time to work on the final touches.

What happened this week was incorporation of a few (more than few, I would say!) tweaks – there were quite a few challenges there and very less time. I guess this 10-week period is to make you realise how you dynamic you get with decision-making, lol!

Jokes apart, I faced some challenges. Testing was executed with six different users, different ages, different backgrounds and different tech-savvy experience. That was great, but more the users, more problems you face. Each tester had their own unique computer, browser and other settings!!! Hard to please everyone, I guess…you can just do your best but one thing for sure – you get to narrow down some basic issues you never noticed. The other big challenge (still is!) is the browser compatibility. with my format, the placement of some divs does not look great in some browsers but works amazingly correct in the others. How do you resolve that issue?

But this was a great Capstone project to document. I enjoyed each week discoveries and assignments which paved the way slowly and steadily towards completion. This week we’re presenting our final project to our peers and it’ll great to have more feedback.

This week is testing time. We’ve worked on our website sufficiently enough to give it a test. Also, as Adam noted, we’ve looked at our website enough to get the third person give it a try! Sometimes the third eye helps 🙂

By Adam’s notes, we have to test the website in three areas: accessibility, functionality, and usability. Here are short descriptions of each:

  • Functionality – Does the website’s functionality work? (hyperlinks, images appear, forms can submit, registration or login features function, etc.)
  • Accessibility – Does the site appear correctly on various operating systems, browsers, monitors, etc. that you expect your audience to use?  (I did talk a little on this in one of my previous posts)
  • Usability – Can the website be used by your audience to accomplish their goals? Can they find what they search for? Are there clear answers to questions they are likely to have?

Links from our instructor, Adam:

http://www.adobe.com/devnet/articles/usability_testing.html

http://www.experiencethread.com/articles/documents/article45.pdf

http://techdocs.tamu.edu/webspace/websitetesting/?searchterm=testing%20checklist

I’ve sent the testing plan document out to a variety of people, different backgrounds, different tech backgrounds, different perspectives. Let’s see what the test results bring in.

I am referring to the Web development process, very often referred to as the six-stage process:

We learned this as a part of John Horn’s “Starting and Running a Successful Website” course and it makes it easier to break down this HUGE task of creating a website so easy.

  • Assessment (preliminary questionnaire, competitor analysis)
  • Analysis and Planning (site goals, target audience, roles and scope)
  • Design (Main template, content, site map)
  • Production (drafts with page look and feel and functional aspects)
  • Testing and Publish (functional, usability testing, etc)
  • Maintenance (SEO, visitor tracking, analytics, etc.)

I am in the process of reading Web ReDesign 2.0: Workflow that Works (http://www.web-redesign.com/) and it too does a great job to explain this.

The other links I found on these are:

http://www.quantumcloud.com/web-design-process.php
http://www.jjg.net/elements/pdf/elements.pdf
http://www.webdesignfromscratch.com/design-process/web-design-process/