sccc.premiumdw.com

WEB105 > Quality Assurance Testing

You’ve built your site, now make sure it works!

• Quality Assurance is one of the most often skipped steps… Do not skimp on Quality Assurance!
• You generally need about ten percent of your overall time to track and fix mistakes; spelling errors, orphan links, misplaced content, etc.
• Every site will need to be checked against scope requirements, across browsers, platforms and operating systems

Alpha Testing

Alpha Testing is an internal set of testing to ensure quality assurance of your product.

• The QA lead or the project manager coordinates creates and tracks all planned tests and assigns team members to sections of the site for testing
• The assigned team member then goes through their part of the site and compiles a list of bugs for the production team to fix

You may use formal bug tracking system software or keep a written document or spread sheet of bugs:

http://www.bestshareware.net/download/img6/web-based-bug-tracker-big.gif

See Also: http://www.bugzilla.org/

What to Test

Since we need to make sure our site works, we need to make sure that we test it completely.

A) Design

• The design team has the keen eye to catch the design mistakes
• Photos may be mistreated, text may not follow the style sheets, etc
• Have the art director/designer check on both platforms and on all browsers

B) HTML/CSS

• The production team should confirm that all tables, cells and graphics are lined up correctly
• Sometimes bug fixes will tweak the original code

C) Functionality/Engineering

• The developers should make sure that all DHTML, JavaScript, Databases, etc. are working correctly

D) Content

• The copywriter/editor should confirm that all headlines are reading as headlines, that body copy reads like body copy, etc.
• Make sure that the content formatting is appropriately applied and that everything is lining up correctly