The Financial Processing & General Ledger Test Plan describes the detailed information for functional testing as input to the implementation project plan.

Financial Processing & General Ledger

Author: Tony Lombardo
Created on: 07/21/2010
Last Modified on: 04/26/2011
Draft status

Testing Dashboard

Milestones tracking test plan progress as well as testing project process.

Initiation

Planning

Discovery

Development

Execution

Analysis

Closing

(tick)

(tick)

(tick)

(warning)

 

 

 

Introduction

Summary of testing project goals and success criteria.
This test plan reviews:

  • Existing project information.
  • Business Requirements and critical components to be tested.
  • Testing types and strategies to be implemented.
  • A proposed testing schedule and deliverables.
Test Items

Items that are not a part of the test plan but may be used as input to the test plan.

In Scope

Identify all features and combination of features to be tested.
Identify type(s) of testing to be performed for this project (i.e. Business Process Testing; Load Testing).

Out of Scope

Identify all features and combination of features not to be tested.
Identify type(s) of testing that will not be performed for this project (i.e. Business Process Testing; Load Testing). Provide reasons.

Out of Scope But Critical to Project Success

Identify any dependencies that my affect the project.

Approach

Describe the overall approach to testing. Specify the approach that will ensure the features in scope will be adequately tested.

  • Test Planning & Preparation - Develop test plan and test schedule and work with BAs, BPOs, SMEs, and technical resources to identify and build the items required for test execution.
  • Test Execution - Conduct the testing utilizing the deliverables from the test preparation stage.
  • Test Reporting & Validation - Metrics and measures that will be reported with regard to the testing in progress or that has been conducted that documents errors and compares actual results to the documented expected results.
  • Test Management & Control - Meetings, Communications, Reviews, Issue & Defect Management

The test plan approach plan incorporates the following guiding principles:

  • Early up-front planning facilitates starting tests on time and staying on schedule.
  • Test the most important and highest risk features first. The testing effort should be sequenced based on identified risk priorities.
  • Test as early as possible. It is less costly to fix errors earlier in the systems development life cycle than later.
  • Test script development must be based on business requirements and functional specifications.
  • Ensure that gaps and overlaps in testing are minimized by clearly defining the objectives of each test stage.
  • Develop well-documented, repeatable test models to facilitate defect analysis during the implementation and establish best practices for a sustainable plan for future work.
  • Determine validation and verification techniques for each test stage to facilitate quick detection of problems.
  • Test with appropriate subject matter expert (SME) and end-user involvement. They have the business expertise to confirm that the application meets business requirements.
  • Testing will begin with a smaller number of project testers to allow for increasing of skills and understanding of the system functionality and processes. As the testing phases progress, the number of testers may increase.
Items Pass/Fail Criteria

Error rendering macro 'excerpt-include'

No link could be created for 'KFS QA Strategy'.

Suspension Criteria and Resumption Requirements

In the event that system testing is suspended, resumption criteria will be specified and testing will not re-commence until the software meets these criteria. Specific testing activities that must be repeated when testing is resumed will also be identified.

Test Deliverables

Identify the test documents associated with this plan.

Specify both the necessary and desired properties of the test environment, identify any other testing needs.

The environments that will be utilized for testing are identified below, along with identifying the test phase usage.

#

Name

Description

Test Phase Utilization

1

KFS TEST

Main Testing environment: Internal testing of application, modifications, reporting, and integration and/or interfaces with other systems.

KFS QA Module & System Integration Tests

Configuration Management

Identify Configuration Management tasks to ensure system being tested is under Configuration Management control. May be a link to a Configuration Strategy document and/or Environment Strategy Document (environment refresh process) if the processes identified in those documents relate to the system being tested. Oracle Enterprise Manager Grid Control can be used to view configuration information.

Monitoring

Identify steps to ensure system being tested is monitored for performance and historical performance information is being collected. Oracle Enterprise Manager Grid Control can be used to monitor and collect performance information.

Team Member and Stakeholder Assignments

Identify the individuals or groups responsible for managing, designing, preparing, executing, witnessing, checking, resolving and signing off on related test plan items.
The following resources will be completely or partially dedicated to the testing effort. The roles each will play in the testing phase.

Table 1: Assignments and Roles

Name

High-level Testing Assignments

Assigned Deliverable

Andy Slusar

KFS Product Owner and Team Lead

2

Susan Wakshlag

KFS Testing Coordinator

 

Mel Radcliffe Jr

Environment Lead/CM

3

TBD

Testing SME

 

TBD

Automation SME

1,4,5

Sandy Eccleston

Technical Implementation Analyist (TIA)

 

Sherry Wilson

Business Analyst

6

Barb Sutton

Functional Lead

 

Cathy Salino

Module Lead

 

TBD

Project Manager

 

Tony Lombardo

QA Lead

1,4,5

Deliverables
1. Test Plan and/or Test Specification document - (Test Group)
2. Test Phase time period listed in KFS project schedule -(KFS Proj Mgr)
3. Overall Test Environment Specs (# of servers, DB, etc). - (KFS team/IS-CM)
4. Test tool selection
5. Test case repository selection
6. Requirements selection

Staffing and Training Needs

Identify staffing and any training needs for this testing project. Both automation and manual testers may need training on the systems or applications being tested. Training may included reviewing the test plan and testing tasks for manual testers.

Testing Tasks and Proposed Schedule

Unknown macro: {table-plus}

Test Plan

Milestone/Deliverable

Start Date

Est. Comp Date

Actual Comp. Date

Test Plan Initiation

07/26/2010

07/26/2010

07/26/2010

Test Plan Completed

10/22/2010

10/22/2010

TBD

Test Plan Approved

10/25/2010

10/25/2010

TBD


Test Project
FP&GL Module Testing Schedule

Gantt chart

Unknown macro: {csv}

Phase, Start, End, Percent
Complete, Owner
FP&GL - Initiation, 07/26/2010, 07/30/2010, 100%, Cathy Salino
FP&GL - Planning, 08/05/2010, 08/20/2010, 100%, Cathy Salino
FP&GL - Discovery, 08/23/2010, 10/22/2010, 100%, Cathy Salino
FP&GL - Development, 10/25/2010, 12/10/2010, 20%, Cathy Salino
FP&GL - Execution, 12/13/2010, 03/11/2011, 0%, Cathy Salino
FP&GL - Analysis, 03/14/2011, 03/14/2011, 0%, Cathy Salino
FP&GL - Closing, 03/14/2011, 03/14/2011,0%, Cathy Salino

Risks and Contingencies

Identify risks and assumptions for testing items in scope. Assign risk priority numbers to individual tests or test sets. Provide contingency plans for mitigation.

Approvals



No files shared here yet.
  • No labels