CM Pros Resources > Website

Website Test Plan

Bug Categories

Functionality - all requirements in our requirements doc should be traceable in our testing. Any requirements in the requirements doc that are not implemented or not implemented as specified in the requirements doc should be classified as a functionality bug.

Usability - these bugs are more of a judgment call. If you feel that the way a requirement has been implemented may confuse an average user, please label this a usability bug. These will be a lower priority than functional or technical bugs, but nevertheless very important.

Technology - Standards/Compliance, including 508 accessibility, XHTML. If you run across any errors or problems in different browsers, this is where these bugs should tracked. Browser/OS requirements should be found in our requirements doc.

Make sure you assign all bugs (to Stuart, Bob D., others). After a bug has been corrected, we will close the bug and the person that originally logged the bug will be sent an email alerting them that the bug has been closed and is ready for re-testing. After the bug has been verified squashed by the original author, they should then change the status of the bug to close. If you've never used Mantis before there is a simple FAQ available at the site.

Elements of our Test Plan

Personas

Scenarios (Use Cases)

Web-based issue reporting and bug tracking

Specific testing steps

Browser testing
Page/Element testing
- Page title correct?
- Page metadata - general plus page-specific keywords
- Page links all working?
- Are secure links secure (https)?
- Page styles correct (h2, h3, h4 in right places?)
- Images have alt attributes
Template testing
- Home page template
- Six main templates
  - About CM Pros
  - Membership
  - Resources
  - Education
  - Events
  - Organization
- Special page templates
  - Calendar
  - Member Directory
  - Job Board
  - Resources Library
  - Best Practices
  - Glossary
  - Shopping Cart