Wyoming DFS

FAMIS Development/Implementation RFP-0302-G

Regression Test Plan Template

T018003

Date Created: March 20, 2002

Revision Date: March 18, 2004

Prepared by

Albion Government Services

and
Wyoming DFS
1. Copyright Statement

Copyright 2009 by Albion Government Services and Wyoming Department of Family

Services, All Rights Reserved.

No part of this publication may be reproduced, transmitted, transcribed, stored in a

retrieval system or translated into any language in any form by any means without the
written permission of the Wyoming Department of Family Services.

Products or corporate names may be trademarks or registered trademarks of other

companies and are used only for the explanation and to the owner's benefit, without
intent to infringe.

12048523.DOC ALBION GOVERNMENT SERVICES WORKING COPY IF

AND WYOMING DFS PRINTED

PAGE 2 OF 12
 2. Table of Contents

1. COPYRIGHT STATEMENT................................................................................2

2. TABLE OF CONTENTS.....................................................................................3

3. CONTEXT...........................................................................................................4

4. DOCUMENT HISTORY......................................................................................5

5. REFERENCES...................................................................................................6

6. QUALITY RECORDS.........................................................................................7

7. REGRESSION TEST PLAN...............................................................................8

7.1. Introduction..............................................................................................................................................8
7.2. Purpose.....................................................................................................................................................8
7.3. Component(s) Being Tested......................................................................................................................9
7.4. High Level Requirements For Testing.....................................................................................................9
7.5. Test Strategy..............................................................................................................................................9
7.6. Entry Criteria for Regression testing.......................................................................................................9
7.7. Exit Criteria for Regression testing.......................................................................................................10
7.8. Test Schedule..........................................................................................................................................10
7.9. Assumptions/Constraints........................................................................................................................10
7.10. Resource Requirements .......................................................................................................................11
7.11. Topologies..............................................................................................................................................11
7.12. Test Cases.............................................................................................................................................11

TO BE FULLY QUALIFIED BY DFS...................................................................11

ACCEPTANCE ...................................................................................................12

12048523.DOC ALBION GOVERNMENT SERVICES WORKING COPY IF

AND WYOMING DFS PRINTED

PAGE 3 OF 12
3. Context

This document provides a Regression Test Plan Template to the project team for the
FAMIS Development/Implementation RFP-0302-G.

Changes to the procedure can and will only be made after approval and written consent
of both Albion Government Services and Wyoming DFS.

This document, ‘T018 Regression Test Plan Template’, supercedes all previous
versions.

12048523.DOC ALBION GOVERNMENT SERVICES WORKING COPY IF

AND WYOMING DFS PRINTED

PAGE 4 OF 12
4. Document Histor y

Version Date Author Comments

1 03/07/02 Phil Holyoake Draft for Peer review
2 03/29/02 Phil Holyoake Approved for Use
3 03/18/04 Richard Krahl Updated for the @Vantage Platform

12048523.DOC ALBION GOVERNMENT SERVICES WORKING COPY IF

AND WYOMING DFS PRINTED

PAGE 5 OF 12
5. References

Document ERoom Folder

P007 Testing Procedure Wyoming FAMIS/Project Procedures

Identify all the project documents and references used for developing this test plan.

12048523.DOC ALBION GOVERNMENT SERVICES WORKING COPY IF

AND WYOMING DFS PRINTED

PAGE 6 OF 12
6. Quality Records

Enter all documented Quality Records that are produced as a requirement of the
document.

Record and description and type (e.g. Minimum Where Retained Restricted
Electronic, paper) Retention Access?
Period
Test Plan (Paper) 2 years* Testing log No
Test Report (paper) 2 years* Test Reports No
*Following the project completion date.

12048523.DOC ALBION GOVERNMENT SERVICES WORKING COPY IF

AND WYOMING DFS PRINTED

PAGE 7 OF 12
7. Regression Test Plan

General:
Please try not to deviate from this template. If it does not fulfill your needs, then discuss
with your team leader for a resolution.
Italicized portions of this document (like this very sentence) are for explanatory purposes
only & should not be included in a completed Regression Test document.

1) The objective of the regression test phase is to ensure that all code changes that
occurred in later executions of project integration and large volume testing have not
had a negative impact on the validity of earlier tests.
2) The regression test will cover all applications that may have been affected by some
program change implemented during the project integration or large volume test
phases. This test will only be executed if the Project Management Team deems it
necessary to retest some of the scenarios included in the project integration phase. If
the project believes that all code changes have already been retested in the project
integration tests, then this phase of testing would be unnecessary. It should be noted
that for problems, which have a data origin, part or all of the conversion tests may
need to be rerun in regression testing.

7.1.Introduction
This document describes the approach for the Regression testing for the IRIS
Application. The Rational TestManager tool set will be the container for all Regression
based tests. As with unit & integration testing, a method/checklist and the test results log
will be used to verify/validate the regression test. The Integration and unit test scripts
may be used as the basis for the regression test scripts.

7.2.Purpose
The purpose of the Regression test plan is to explain what Regression testing
accomplishes. In brief, Regression testing is the selective retesting of a software system
that has been modified to ensure that any bugs have been fixed and that no other
previously working functions have failed as a result of the reparations and that newly
added features have not created problems with previous versions of the software.

12048523.DOC ALBION GOVERNMENT SERVICES WORKING COPY IF

AND WYOMING DFS PRINTED

PAGE 8 OF 12
7.3.Component(s) Being Tested
Identify the existing project information and software components that should be tested.

7.4.High Level Requirements For Testing

List the recommended high-level requirements for testing. Identify the Use cases,
functional requirements and non-functional requirements that have been identified as
targets for testing. The list below should represent the details of each test conducted
during each of the iterations in each of the phases of Inception, Elaboration and
Construction.

7.5.Test Strategy
The Test Strategy presents the recommended approach to the testing of the software
applications. The previous section on Test Requirements described what will be tested;
this describes how it will be tested.

The main considerations for the test strategy are the techniques to be used and the
criterion for knowing when the testing is completed.

In addition to the considerations provided for each test below, testing should only be
executed using known, controlled databases, in secured environments.
Each type of testing should clearly specify the following:

1) Test Objective
2) Technique
3) Completion Criteria
4) Special Considerations

7.6.Entry Criteria for Regression testing

Identify the Entry Criteria. For example:

1) Approved Regression Test Plan

2) Some fixes will be regression tested by re-running cycles of the project integration
test before they have been signed off. The initiation of the 'formal' regression test
should occur after the completion of the project integration test and large volume test
phases.

12048523.DOC ALBION GOVERNMENT SERVICES WORKING COPY IF

AND WYOMING DFS PRINTED

PAGE 9 OF 12
 3) Regression test should be run before the simulation/user acceptance test so that the
system is as error free as possible at that point. If the simulation/user acceptance test
results in more fixes being made then management should decide which if any of the
regression scenarios should be rerun.
4) Coding changes completed

7.7.Exit Criteria for Regression testing

Identify the Exit Criteria. For example:

1) Regression testing complete

2) Test records produced
3) Fault records produced and resolved
4) Test approved by reviewer and authorized by Test Coordinator

7.8.Test Schedule
Identify the test schedule for the particular component(s) you are testing. For example,
the initial unit test for this component(s) should be completed in 2 hours, or 1 day, or 3
days. Identify all steps required in setting up the test.

7.9.Assumptions/Constraints
Testing results could be hindered or otherwise affected by the lack of any one of the
following items:

1) Hardware resource availability - stand-alone Acceptance environment will be needed

2) Stable source control area
3) Requirement and or design exit criteria
4) Ability to mimic real-time end-user (pilot) environment
5) Tool availability
6) Accurate Design Document
7) Resolved Defects/Change Requests
8) Training / knowledge building
9) Sufficient number of test personnel

12048523.DOC ALBION GOVERNMENT SERVICES WORKING COPY IF

AND WYOMING DFS PRINTED

PAGE 10 OF 12
7.10.Resource Requirements

7.10.1Hardware Requirements
Identify the Hardware Requirements

Resource Description Qty

Hardware Requirements eRoom Hardware Inventory Folder TBD

7.10.2Software Requirements
Identify the Software Requirements

Software Description Qty

Software Requirements eRoom Software Inventory Folder TBD
7.10.3Personnel Requirements
Identify the Personnel requirements and skills.

7.11.Topologies
The topologies required for performing the tests may be mentioned in this section, with
schematic representation wherever necessary.

7.12. Test Cases

TO BE FULLY QUALIFIED BY DFS

All the test cases may clearly be defined here in this section. Each Test Case must
clearly specify the following:

1) Identification of the test Case

2) Pre-condition for the tests
3) Input conditions
4) Actions to be taken
5) Expected Result
6) Method for validating the expected results

12048523.DOC ALBION GOVERNMENT SERVICES WORKING COPY IF

AND WYOMING DFS PRINTED

PAGE 11 OF 12
Acceptance

Deliverable Name: Deliverable Number:

Regression Test Plan T018
Project Manager: Phase:
Todd Norris Regression Testing
Delivery Date: Acceptance Request Date:
Month DD, YYYY Month DD, YYYY
Findings:

Acceptor Comments:

Acceptance Accepted Rejected

Disposition:
Albion Government Services Wyoming DFS
Name: Name of Person Signing Name: Name of Person Signing

Title: Title of Person Signing Title: Title of Person Signing

Signature: Signature:

Date: Month DD, YYYY Date:

Name: Name of Person Signing

Title: Title of Person Signing

Signature:

Date: Month DD, YYYY

12048523.DOC ALBION GOVERNMENT SERVICES WORKING COPY IF

AND WYOMING DFS PRINTED

PAGE 12 OF 12