Article Menu

Sunday, 02 November 2008 20:00

Test Plan

Written by  Jonathan Malkin
Rate this item
(0 votes)

Last month I discussed the justification for testing.  Here are the minimum testing requirements of any organization.  If you are a client purchasing software or contracting for the development of software, then consider requesting proof that it actually works.

Acceptance Tests
Responsibility: Quality Control
  • QC develops acceptance tests for key system features
  • QC adds to the acceptance test suite as new features are implemented or customers contract for customizations
Unit Testing
Responsibility: Developers.
  • Developers write unit tests as an integrated part of the code base
  • In many cases the test code will be as large as the system of test
Release
  • A developer does not release code until
    • The code is written
    • All unit and acceptance tests pass.
    • All requirement and test case documents match and accurately reflect the actual code delivered.
  • Three Components of any Release 
    • Code Base 
    • Testing Base 
    • Documentation

Defect Resolution

  • Unit and acceptance tests are written to replicate any reported bugs. 
  • The entire test suite, including the new tests, is executed to ensure the bug has been      resolved and no new bugs have been introduced.
Read 1065 times Last modified on Tuesday, 27 March 2012 13:46
Published in Jonathan Malkin
More in this category: « Federal Government Reducing the Cost of Change through Software Testing »

Add comment

back to top