AFESWeb and AFES Clarify Test Plan

Software Test Plan

For

AFESWeb andAFES Clarify

Version 6.0

Prepared By:

Chapter Corporate Information Systems Test Engineering

American Red Cross

May 24, 2006

CI #: CCIS-DI-AFES-0130-1.0.0

Table of Contents

CI #: CCIS-DI-AFES-0130-1.0.0

1.Introduction

2.References, Acronyms, Terms and Abbreviations

3.Test Items

4.Features and Functions to Test

5.Test Strategy and Procedures

6. Entrance Criteria

7. Exit Criteria

8. Test Deliverables

9. Test Environment

10. Test Schedule

11. Risks and Assumptions

Authorizing Signatures

APPENDIX A– Requirements Traceability Matrix

1.Introduction

This is a working document and will be added to or modified throughout time as needs arise. Any questions regarding the information contained in this document should be directed to Ross Johnson, Project Manager, Polly Trammel, Requirements Analyst,Jonathan Link, Director of Test Engineering, or Mallika Padala, Test Engineer.

The purpose of this document is to define the Test Plan for the functional testing of the AFESWeb and AFES Clarify version 6.0 and provide a framework for the testing effort in order to verify functionality per design specifications. This will be accomplished by defining a detailed, comprehensive plan for testing the automated system running within the AFESWeb application and also AFES Clarify application. The software testing will be conducted using similar hardware types and configuration as expected operationally.

American Red Cross (ARC) Armed Forces Emergency Services (AFES) helps military members and their families by providing emergency services in times of need. Some examples include around-the-world communication to service men and women, financial assistance, etc. A number of service centers or chapters that are located throughout the world provide these services. Subsets of these service centers use the product Clarify to manage emergency service cases. As part of the continuing upgrade of AFES, ARC has decided to provide access to case data managed by Clarify to a larger number of authorized AFES staff by providing case status lookup, service delivery reports, and limited administrative functions, over the World Wide Web. The first version of this effort was initially called WebLite and later renamed to A

FESWeb.

2.References, Acronyms, Terms and Abbreviations

The following applicable documents, of the exact issue shown, were used as reference and guidance in the development of this plan:

  • Software Requirements Specifications (SRS) for AFESWeb/AFES Clarify release 6.0 (CM# CCIS-DI-AFES-0129-1.00)

Acronyms, Terms and Abbreviations

AFESArmed Forces Emergency System

ARCAmerican Red Cross

CMConfiguration Management

CCISChapter Corporate Information Systems

MRBManagement Review Board

QSMQuality Systems Management

RTMRequirements Traceability Matrix

SPRSoftware Problem Report

TRR Test Readiness Review

3.Test Items

The scope and objectives of this Testing activity will include:

Develop the Test Plan - This will describe the approach, test conditions, test environment and a layout of the test cases being used during manual testing.

Prepare the Test - Development of test cases with expected results.

Update RTM – Update RTM with Test cases associated to specific requirements.

Execute the Test - Includes the execution of test scripts identification of incidents, tracking of SPRs, and regression testing of the system.

This Test Plan establishes criteria for evaluating the effectiveness of the AFESWeb and AFES Clarify system software testing performed for the purpose of finding problems before release. The test activities and procedures represent those deemed effective for determining that the test effort has been successful.

All dry run and formal testing will take place at the ARC NHQ,431 18th St NW, WashingtonDC20006.

4.Features and Functions to Test

The following is a list of new features and functions that will be tested in this release of AFESWeb V 6.0:

Temporary Contact Information

Display User Registration Information

Welfare Information Label Change

Display Rank drop down

Enhanced Search by Name

Default All Text to Upper Case

Display Password Error Message

Hyperlink to Case Information Screen

Add Alternate Phone Number

The following is a list of new features and functions that will be tested in this release of AFES Clarify V 6.0:

Display Military Phone Number on Printed Case Report

ModifySU in Closed Sub Case

DisplayModification of SU at the Sub Case Level on the Case Activity Log

Display Modification of SU at the Case Level in the Case Activity Log

Display Modification of SDU at Case Level in Case Activity Log

Modify Calendar Wizard

Assign Multiple Users to Queues

Change Queue Dispatch Search Default

Sort Options for Select Employee

It is the intent of the test department to test all related features with these new enhancements.

5.Test Strategy and Procedures

The test strategy focuses on testing AFESWeb and AFES Clarifyas an overall System. By testing the associated test cases and procedures, the test program should demonstrate sufficient evidence of AFESWeb and AFES Clarify functionality.

Test cases consist of two types: Informal and Formal.

Informal: Test cases consisting of unit or integration testing conducted without the use of a set of written procedures.

Formal: Test cases consisting of integration and system level testing conducted using a formal, written set of test procedures.

For any issues that are found during the testing of AFESWeb and AFES Clarify version 6.0the following steps will be followed:

  • Software Problem Reports (SPR) will be opened in the issue-tracking tool. For this release we will be using Test Director
  • SPR lists will be provided for review during test cycle by the test group. The management review board (MRB) members review the SPR lists and provide feed back on any issues that should be rejected, investigated or deferred to a later release.
  • A Software Test Report will be used after testing to document the general results of the test, including which requirements failed and the status of all SPRs written.

Test Engineering will coordinate, oversee and perform the following activities:

  • Ensure that required resources are scheduled and that preparations for test execution are complete
  • Ensure that pre-test conditions and assumptions are met prior to initiation of the test
  • Conduct pre/post-test briefings/debriefings
  • Coordinate the activities of the test participants

The Test Engineers will be designated to operate the AFESWeb and AFES Clarify version 6.0 subsystems under the direction of the Director of Test Engineering and the Project Manager. During the testing, the Test Engineer will have the following responsibilities:

  • Initiate execution of the test from a data entry terminal
  • Perform user functions at a workstation in accordance with applicable test procedures
  • Collect data and perform analysis as required.
  • Prepare a Software Test Report.

Test Case Descriptions

Please refer to Appendix A for a complete list of test cases and requirements for this release. Test cases can also be viewed in Test Director.

6. Entrance Criteria

A Test Readiness Review (TRR) will be conducted prior to each test cycle. The TRR will include the following information:

  • The build being complete and turned over to test
  • Test Drop Report will be provided to the entire team
  • Test Cases associated with the current cycle
  • Test environment status
7. Exit Criteria

The test cycle will be considered complete when all of the test cases scheduled for the cycle have been executed and validated. SPRs that passed testing during the cycle will be Verified and Closed by the testing team. A list of Closed SPRs, a Software Test Report, and Test Results documents will be provided to Configuration Management at the end of testing. A list of outstanding SPRs will be presented at the end of the test cycle and brought to MRB.

All Critical and High priority issues will need to be addressed before moving onto production.

After the conclusion of all scheduled system test cycles, a Production Readiness Review (PRR) will be conducted.

8. Test Deliverables

The test deliverables for AFESWeb 5.1.0.0 and AFES Clarify 5.1.0.0 are listed in the table below:

Test Deliverables / Purpose
Software Test Plan / Documents the AFESWeb and AFES Clarifyversion 6.0 Test Objectives and Approach (this document).
Test Cases document / A list of test scenarios and cases for each type of testing to be conducted during system test.
Software Test Report / A summary of final test status and defect statistics as well the test case document with actual test results and status for each test case and a list of prioritizing outstanding defects will be provided at the end of each test cycle.
9. Test Environment

A test facility is established at the American Red Cross that provides an uncontrolled environment for the conduct of the test. Several different programs and personnel are conducting various testing activities at the same time, access is unrestricted, and there is no assurance that test equipment has not been corrupted. Hardware and software configuration requirements for testing are listed below:

Database Server

Clarify Client 12.5

Oracle Client 9i

AFESTST1

Client-side Environment

Windows 2000

Microsoft Office 2002 sp2

Internet Explorer (IE) 6.0

10. Test Schedule

AFESWeb and AFES Clarify version 6.0 is scheduled to go into production on July 5, 2006.

Note: Test Days are tentative and may be revised based on previous test results and iterative development.

Cycle / Type of Test / Days in Cycle (approximate)
First Test Cycle /
  • Functionalities test
/ 7 days
MRB
Second Test Cycle /
  • Fixes/test
/ 3 days
MRB
Third Test Cycle /
  • Regression test
/ none
MRB

A post-test briefing will be held following testing to discuss the results of the test. MRB’s will be used after each round of testing to discuss and prioritize which issues will be worked for this release and which can be deferred or rejected.

11. Risks and Assumptions

The following seeks to identify some of the more likely project risks and possible contingencies:

  • No testing of the system done using 56k modem connection.
  • Lack of accurate data to run reports. Made up data may not reflect the accurate data used by the customer. Data used will be created to effectively generate reports, accurate data would help ensure business functionality is being met.
  • Delays in development result in delays in testing.
  • No database refresh is being made with more current data.
Authorizing Signatures
Prepared By: / Approved By:
Signature / Date / Signature / Date
Title / Title
Department: / Department:
Approved By: / Approved By:
Signature / Date / Signature / Date
Title / Title
Department: / Department:
Approved By: / Approved By:
Signature / Date / Signature / Date
Title / Title
Department: / Department:
APPENDIX A– Requirements Traceability Matrix
SRS # / Requirement Description / Clarify Case Number / SDD# / Test #
AFES Web
WEB-1 / Temporary Contact Information
WEB 1.1 / The First Name data entry field shall be removed from the existing Temporary Contact Information screen
WEB 1.2 / The text field “First Name” shall be removed from the existing Temporary Contact Information screen
WEB 1.3 / The Last Name field data entry field shall be removed from the screen
WEB 1.4 / The text field “Last Name” shall be removed from the screen
WEB 1.5 / The system shall auto populate the Phone Number field on the Temporary Contact screen with the Phone Number from the user profile.
WEB 1.6 / The system shall allow the user to edit the Temporary Contact Phone Number
WEB 1.7 / The system shall auto populate the Email Address on the temporary contact screen with the Email Address of the user profile
WEB 1.8 / The system shall allow the user to edit the Temporary Email Address
WEB 1.9 / The text field that reads “ enter SDU number or the city and state of the SDU” shall be removed from the temporary contact screen
WEB 1.10 / The SDU Number text label shall be removed from the screen
WEB 1.11 / The SDU Number data entry field shall be removed from the screen
WEB 1.12 / The text label “city” shall be removed from the screen
WEB 1.13 / The data entry field for city shall be removed from the screen
WEB 1.14 / The text label “state” shall be removed from the screen.
WEB 1.15 / The state data entry field shall be removed from the screen.
WEB 1.16 / Requirement removed
WEB 1.17 / The Temporary Contact Information screen shall be displayed to the user during Case Create (Local Only),
WEB 1.18 / The Temporary Contact Information screen shall be displayed to the user during Case Create (Shared)
WEB 1.19 / The Temporary Contact Information screen shall be displayed to the user during Case Update
WEB 1.20 / The Temporary Contact Information screen shall be displayed to the user during Disaster Case Create.
WEB 1.21 / The Temporary Contact Information screen shall be displayed to the user during Welfare Inquiry Case Create
WEB-2 / Display User Registration Information / 917686
WEB 2.1 / The system shall display the following information on the AFESWeb login screen: “For any assistance with AFESWeb, please contact User Support at 888-778-7762. If you are calling from the DC area or outside the United States or Canada, you can call 703-206-6011.”
WEB 2.2 / The system shall display the following information on the AFESWeb Login screen: “The AFESWeb Information Page is available at::”
WEB 2.3 / The system shall display the following link to the AFESWeb Information on the AFESWeb login screen: ”
WEB 2.4 / The system shall display the following on the AFESWeb login screen: “Should you need to register a user, please go to the above link and click on “Register” to obtain the form. Instructions for completion are on the form.”
WEB 2.5 / The system shall remove the existing text from the AFESWeb Login screen: “Need Help Signing in? Click Here”
WEB 2.6 / The system shall remove the following text from the screen: “Rick Davis, Director Emergency Communications”
WEB-3 / Welfare Inquiry Web Page Text Change / 902794
WEB 3.1 / The system shall replace all references to “Welfare Inquiry (WI) ” with “Welfare Information (WI)” on all user interface screens and links. These included but may not be limited to:
  • Welfare Inquiry Case Create
  • AFESC/MASRU/Response Reports Screen
  • Welfare Inquiry Report Screen
  • Welfare Inquiry (WI) Case Information Screen
  • AFESWeb Main Page
  • Welfare Inquiry Add Service Page

WEB-4 / Display Rank Drop-down box / 883987
WEB 4.1 / The existing Rank field drop down box on the Case Create (shared) screen shall be enlarged to allow the entire text entry in the Rank field to be visible to the user.
WEB 4.2 / The existing Rank field drop down box on the Case Create (local only) screen shall be enlarged to allow the entire text entry in the Rank field to be visible to the user.
WEB 4.5 / The existing Branch field drop down box on the Case Create (shared) screen shall be enlarged to allow the entire text entry in the Rank field to be visible to the user.
WEB 4.4 / The existing Branch field drop down box on the Case Create (local only) screen shall be enlarged to allow the entire text entry in the Rank field to be visible to the user.
WEB-5 / Enhance Search by Name / 845474
WEB 5.1 / The system shall allow the user to request a search for a case using the following mandatory parameters:
Last Name
First Name
Case creation date range
WEB 5.2 / The system shall allow the user to access this search on the AFES/MASRU/Response report screen
WEB 5.3 / The system shall allow for a wild card search for the first name with a minimum of one character.
WEB 5.4
WEB 5.5 / The system shall allow for a wild card search for the last name with a minimum of one character
WEB 5.6 / The system shall compare the requested name with the Service Member Name field in the database
WEB 5.7 / The system shall allow the user to enter a date range for the case creation date
WEB 5.8 / The system shall default the date range to the last 30 days.
WEB 5.9 / The system shall allow the user to edit the defaulted date range.
WEB 5.10 / The system shall allow the user to enter a zip code as an optional search parameter.
WEB 5.11 / If the Zip Code field is populated, the system shall compare the zip code value entered to the zip code value in the Family Individual Information Tab
WEB 5.12 / The system shall display the label “optional” next to the zip code data entry field on the screen
WEB 5.13 / The system shall display the following note on the Search Screen “ NOTE: To increase accuracy of search results, please provide as much information as possible”