back to: Topp QA  

Basic QA Procedure

• Overview
  
  
  • types of testing
  • cycles
    
• How to use Trac

Overview

Somethings to remember.  QA is radically different than the type of testing done in engineering, but has the following in common: regression (bugs need to stay closed) and coverage (everything that might break or be broken needs to be tested). 

Types of Testing:

QA is basically divided into 2 types of testing: user testing and aggressive OCD sabotage imitating the craziest things that users could conceivably do

POA 

We want to do two things: discover bugs and track existing one (and make sure they are close).  People should work in pairs if possible, one person acting as the saboteur (Evil User) and the second acting as the test administrator: filing tickets, making sure the saboteur tests everything, taking notes for future test scripts.

How To Use Trac 

A release(in the customer, not engineering sense) will get it's own ticket for QA.  All tickets that will block a public facing launch will be added to the blockers on this ticket (or simply all tickets that need to be tested, these may also be more specific QA tasks).  

The comments will be used by tester to track what tickets they have confirmed and tested.

New bugs that are found during QA will be added to trac, and, once closed, will be confirmed in subsequent QA sessions.

The Matrix

When testing features related to projects & roles, make sure to test all the permutations laid out in THE MATRIX: