This document is a Test Plan for ICICICenter-Xiii, 2010 January Release produced by Quality Assurance. It describes the testing strategy and approach to testing that QA will employ to validate the quality of the product prior to release. It also contains various resources required for the successful completion of the project, the risks and contingencies involved and the roles and responsibilities of the concerned authorities

A number of different levels of testing may be appropriate within the development methodology.  A hierarchy of plans may be required to provide adequate control of these different levels of testing.  The complexity of the test planning documents will depend on the overall scope of the development project.  For a small project, a single test plan, identifying the appropriate testing levels and tasks, would be appropriate; a project of substantial scope, involving several separate component development activities, may require a series of “nested” test plans.

PURPOSE

The Primary purpose of this document is to establish a test plan for the testing activities that will verify the ICICIC as a high quality product that meets the specified requirements. These activities will focus upon identifying the following:

<!--[if !supportLists]-->·         <!--[endif]-->Overview of the Project

<!--[if !supportLists]-->·         <!--[endif]-->Items to be tested

<!--[if !supportLists]-->·         <!--[endif]-->Test Strategy

<!--[if !supportLists]-->·         <!--[endif]-->Testing Methodology and Approach

<!--[if !supportLists]-->·         <!--[endif]-->Roles and responsibilities

<!--[if !supportLists]-->·         <!--[endif]-->Estimates/Schedule

<!--[if !supportLists]-->·         <!--[endif]-->Release Criteria

<!--[if !supportLists]-->·         <!--[endif]-->Hardware/Software

<!--[if !supportLists]-->·         <!--[endif]-->Risks and contingencies

<!--[if !supportLists]-->·         <!--[endif]-->Test Deliverables

SCOPE

ICICIC January 2010 Release is focused on the Census Issues and ‘New Client Requirements’ implemented in this release. Manual Testing Team is responsible for all types of testing performed on this release and will ensure that existing functionality is not affected for the specified list of clients. The objective of this test plan is to accomplish - using a comprehensive and methodical testing process done by Manual Testing Team.  The primary objective of this process is to uncover the systems limitations and functionality and measure its full capabilities.

See below for detailed process and a brief explanation:

<!--[if gte vml 1]> <![endif]--><!--[if !vml]--><!--[endif]-->

Reference Documents

The table below identifies the documents and their availability, used for developing the test plan.

Code Freeze Date

Scheduled code freeze date for January 2010 release is 12/07/2009. Any items included after would be by exception and approval only. Our assumption is that any code changes made after that date will be implemented for next release.

Change Control

After baseline, all changes must be approved and documented by product development.  If it is agreed that the change is necessary, the impact to development and testing must be agreed upon by the Tester and Director of Quality & Release Management, Manager, Product Development, Product Manager and Sr. VP of Product.  This may (or may not) affect the planned completion date of the product. All changes are updated under change control ticket 12345.

Overview

The ICICI Maintenance Release will be in the January 2010.  This test plan document provides information on testing new features and enhancements to be released in 01/31/2010. Test Plan Documentation is developed using the reference documents from Product Requirements and System Design Documents from product management and development, and also some Census Issues and it explains in detail, how the test activates are planned to test new features in ICICIC and as well as exiting ICICIC

Test Items

This section of the plan should identify all of the elements covered by the testing tasks within the scope of the plan.  Each item to be tested should be unambiguously identified.  The nature of the identifier will in many cases vary according to the level of testing.  Identification may be linked (where possible) to the Configuration Management system; most test items will be identified as configuration items.

New Product Features to Be Tested

Below is a list of features that will be tested. 

Features Excluded from testing

Below is a list of features that will be tested.

Test Matrix

Below is a list of test cases used and developed for testing. 

Read Me