Quality Assurance Strategy

For TSSi MicroSage

 

Strategy Overview

 

The purpose of this QA strategy is to apply process to the task of assuring a quality software product. This quality assurance strategy is segmented into four groups of tests. In most circumstances, each segment should be completed before moving to the next. Regularly released progress reports (from the QA team) will focus on the completion of these test segments. The test segments include the following:

 

  1. Unit Testing
  2. Integration Testing
  3. Report/Query Testing
  4. Special Requirements Testing

 

Strategy Outline

 

This strategy outline breaks each test segment into the steps needed to successfully complete that segment.

 

  1. Documentation of architecture and intended business functionality.
  2. Unit Testing
    1. Identify, describe and outline the functionality requirements of individual application units.
    2. Units will be validated through the following types of tests:
      1. UI/Runtime Testing: This testing will ensure the unit does what is intended on the front end. This includes the testing of every event that can be generated using the unit’s user interface. Examples include screen navigation and display/formatting consistency. No errors should occur under proper use and appropriate handling should occur when improper use occurs.
      2. Data Integrity Testing: This testing will ensure the unit does what is intended on the back end. Data integrity testing confirms that all interactions with the user interface result in correct data presentation, storage and manipulation. This also includes data validation to guarantee clean content.
      3. Performance Testing: This testing will ensure the unit performs in an acceptable fashion. Performance bottlenecks will be looked for and identified.
    3. Design and prioritize the elements of a Unit Test Plan for each unit identified.
    4. Execute the Unit Test Plan.
  3. Integration Testing
    1. Identify and describe unit integration points.
    2. Integration points will be validated through the following types of tests:
      1. UI/Runtime Testing: This testing will ensure the application navigates properly between units.
      2. Data Integrity Testing: This testing will ensure the application’s data is reflected properly between units.
    3. Design and prioritize the elements of an Integration Test Plan.
    4. Execute the Integration Test Plan.
  4. Report Testing
    1. Identify and describe application reports.
    2. Design and prioritize the elements of a Report Test Plan.
    3. Execute the Report Test Plan.
  5. Special Requirements Testing
    1. Validate all completed testing against intended business functionality and identify any special requirements not yet tested.
    2. Design and prioritize the elements of a Special Requirements Test Plan.
    3. Execute the Special Requirements Test Plan.

 

 

 

 

 

 

 

Progress Report

 

Test Segment

Status

Completed

Started

Finished

Unit Testing

l

0%

   

Integration Testing

l

0%

   

Report Testing

l

0%

   

Special Requirements Testing

l

0%

   

Chart Key

l Not Started

¡ On Hold

o In Progress

n Completed

 

 

QA Process Diagram

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Links to supporting Documents

 

Document

Description

Status Report.doc

Project status report.

Unit Test Plan.doc

Outlines the preparation, progress and outcomes of unit testing.

Integration Test Plan.doc

Outlines the preparation, progress and outcomes of integration testing.

Report Test Plan.doc

Outlines the preparation, progress and outcomes of report testing.

Special Requirements Test Plan.doc

Outlines the preparation, progress and outcomes of special requirements testing.