Test Plan

Reserve bank
Detailed Test Plan - UIS

Banking System
This copy printed on: July 16, 2019

Document Last Modification date: July 20, 2020
Version: 0.0
Status: <Draft >
Revision: 1
Document Owner: R BANK PCL.
Document Author: Lavanya
Document Reviewer: <Reviewer/Manager>
Detailed Test Plan - XYZ System
<Version> - <Draft/Revised/Final>
Document History
This is a snapshot of an on-line document. Paper copies are valid only on the day they are
printed. Refer to the author if you are in any doubt about the currency of this document.
This is document template format when you copy to use please remove yellow highlight and
replace with your own information.
Revision History
Version Revision Date Summary of Changes Changed by
Number
V 0.1 08 Nov 2015 Initial Version
Reviewer
Name Position/ Department Version Review Date
(Name-Surname) (Position / Department) 9.9 DD/MM/YYYY
Approvals
Name Position/ Department Version Approve Date
Name-Surname) (Position / Department) 9.9 DD/MM/YYYY
Distribution
This document is available to:
Entire Project
Restricted to the following team members
Name Title
(name) (title)
Document1 (Revision 6) Page 2 of 15
XYZ BANK Confidential

Contents
List of Table.................................................................................................................................... 4
1 Introduction ............................................................................................................................ 5
1.1 Background ...................................................................................................................... 5
1.2 Testing Objectives .......................................................................................................... 5
1.3 Document Audience ........................................................................................................ 5
1.4 References ...................................................................................................................... 6
1.5 Definition and Acronyms .................................................................................................. 6
2 Testable Items ........................................................................................................................ 7
2.1 In Scope .......................................................................................................................... 7
2.1.1 Functional Scope ...................................................................................................... 7
2.1.2 Non Functional Scope ................................................................................................. 7
2.2 Out of Scope .................................................................................................................... 8
2.3 Testing Exclusions ........................................................................................................... 8
3 Detailed Test Approach ........................................................................................................ 9
3.1 Naming Conventions for Function Groups and Functions ............................................... 9
3.2 Test Case Design ............................................................................................................ 9
3.3 Test Scheduling ............................................................................................................... 9
3.4 Data Build ...................................................................................................................... 10
3.5 Results/Sign-Off............................................................................................................. 10
3.5.1 Suspension/Resumption Criteria .......................................................................... 10
3.5.2 Pass/Fail Criteria ..................................................................................................... 11
4 Test Conditions.................................................................................................................... 12
4.1 Business Event 1 - BR001 .......................................................................................... 12
4.2 Business Event 2 - BR002 ............................................ Error! Bookmark not defined.
4.3 Business Event 3 - BR003 .......................................................................................... 12
4.10 Business Event 10 - BR0010 ........................................ Error! Bookmark not defined.
5 Test Environments .............................................................................................................. 13
5.1 Client Side Infrastructure ............................................................................................... 13
5.2 Host/Server Side Infrastructure ..................................................................................... 13
5.3 Middleware .................................................................................................................... 13
5.4 Test Data preparation .................................................................................................... 13
6 Test Schedule ...................................................................................................................... 14
Appendix A - System Schematic/s ............................................................................................ 15

List of Table
Table 3: Reference .......................................................................................................... 6

Table 4: Definitions and Acronyms................................................................................... 6
Table 5: Functional .......................................................................................................... 7
Table 7: Non Functional ................................................................................................... 7
Table 6: Out of Scope Content ........................................................................................ 8
Table 9: Example test cycle .......................................................................................... 10
Table 10: Entry and Exit criteria of testing level ............................................................. 11

1 Introduction
1.1 Background
The Detailed Test Plan (DTP) contains a detailed and executable strategy for conducting. It
defines the detailed testing objective specific to a particular system, the testing approach, test
environment, test conditions, and the test plan.
Target is to concentrate on internal and external fraud detection. The primary

stage will concentrate on the detection of internal fraud at the retail and private
branch operations and at the activity of staff accounts that defined from XYZ bank.
1.2 Testing Objectives

The objectives of testing are as follows:
• Implement a world-class fraud detection system that will be scalable and
expandable and will assist the Bank compact and significantly reduce both
internal and external fraud risk.
• Develop a fraud detection capability that allows the management of multiple
fraud risk types through a common platform.
• Provide a robust fraud detection platform that can be used across multiple
enterprises across the XYZ bank.
1.3 Document Audience
Role Name Email/ Telephone Organization

Product Owner
Project Manager
PMO
QA
Functional Team
Lead
BA
Business Unit
Development
Team Lead
Infrastructure
Team Lead

Role Name Email/ Telephone Organization
Infrastructure
Team
Test Lead
Test Team
Deployment
Team Lead
Deployment
Team
* Remove the role which may not include in your project charter. * If document change version and the
stakeholder name is changed, should modify the name as well..
1.4 References
This document is based on and refers to the following documents:
Table 1: Reference
Document Name Author Version Update date

1. <Master Test plan> <Name of last update person> <V.9.9> <Latest update date>
2. Bank Specification V.0.1 December 27,
2019
3. <RTM : Requirement <Name of last update person> <V.9.9> <Latest update date>
Traceability Matrix>
1.5 Definition and Acronyms

This section provides information regarding the Acronyms and terminology specifically used in
this document.
Table 2: Definitions and Acronyms
Acronym Definition
CD Cash Deposit
CW Cash Withdrawal

2 Testable Items
2.1 In Scope
This test activity focuses on the following:
1. Perform investigations based on business rule.

2.
3.
2.1.1 Functional Scope

To list all functional area and description that will be in scope of testing.
Table 3: Functional
Functional Area Functional Sub Area Description
BR001 BR001_1 Detailed description
2.1.2 Non Functional Scope

To list all non functional area and description that will be in scope of testing.
Table 4: Non Functional
Non Functional Description

Requirement
NFR-001 Detailed description
NFR-002 Detailed description

2.2 Out of Scope
[It is important to clearly define (at a high level) all of the testable components of the
solution that will not be tested. These should include infrastructure, functional subsets,
non-functional requirements, and software modules. Specific testing activities (such as
load and performance testing, penetration tests, etc) should also be listed. Brief reasoning
behind why the items have been de-scoped should be included].
Table 5: Out of Scope Content
Item Description
1 <High level describe the item of out scope>

2.3 Testing Exclusions

[A test exclusion is an element of the SUT that has not been de-scoped but which will not
be tested by this plan due to (usually) a logistical issue. These may include activities such
as report/letters distributed by fax/email/sms and may reference the test phase/level that
will be responsible for conducting this testing].

3 Detailed Test Approach

All testing conducted by, or for, the KT Program complies with the Master Test Strategy.
This DTP has been created to define the test activities documented in the Master Test
Plan
[Insert Release Name and Test Activity] will be tested using the following approach:
[List (in detail) the key elements that make up the strategy you will use to deliver the
required test objectives. Wherever possible link specific activities to the relevant test
objective. Change/edit the accompanying descriptions to suit the individual release].
3.1 Naming Conventions for Function Groups and Functions

[Use the Configuration Management naming conventions to define the structure used for
the test project nomenclature. If HP Quality Center is to be used ensure the nomenclature
rules also align with the requirements defined for it. The Test case ID should be agreed
with the naming convention.
Rename this section as required:

… for Function Groups and Functions
… for Scenarios and Usecases
etc]
3.2 Test Case Design

Extract testable requirements from the requirement specifications and design test
conditions which accurately reflect the functional enhancements and changes.
[Add design elements/requirements specific to this test activity].
Identify test approach about test case design before identify the detail of test case test script in
next step. To declare what is the concern item of each module or functional/non functional area
and what the test case design is for detect the defect. The test technique should be state for this
section. XYZ bank test coverage matrix should be mention and state that how to ensure the
project will follow this guideline.
Test design should mention about the group of regression impact. If the most of the defect occur
on the area which test case design should be re-test. And the regression test approach should be
mention as well.
3.3 Test Scheduling

Identify test schedule for <Test level> base on <project master plan version>. The high level plan
for testing preparation, test execution, defect fixing, and data test preparation period are identified
as below. <The format of schedule can demonstrate in structure of table of calendar or schedule
in Microsoft project>
[For complex test schedules reference any external tools or systems you will be
using/developing to support the scheduling. Include specific flags or nomenclature that
will be used to identify/classify test scripts and test cases that have to be executed at a
specific point in the schedule. (pre or post batch, day one, after script xyz has executed,
etc]

Figures 1: Test schedule
Table 6: Example test cycle
Batch Run # Function to be Executed Cycle Date

Batch Run 1 Account Enquiries TBD *(to be defined)
(Daily) New Account Set-up
Transaction Processing
Batch Run 2 Interest Posting 12/06/09
(Cycle) Minimum Payment
Batch Run 3 Interest Accrual TBD *(to be defined)
(Daily)
3.4 Data Build

Identify plan to get data for each testing area. Mention the approach and activity plan for getting
test data properly. The process step of prepare data mention here.
[Document the strategies that will be used to generate or extract appropriate data for the
test effort].
3.5 Results/Sign-Off
3.5.1 Suspension/Resumption Criteria
Testing will halt for a particular project item (or function) when:
 A critical problem is identified and where the potential code fix will require substantial re-
testing of that function
 It is identified that the business or technical specifications require major modifications due to
escalated test issues and those modifications would require additional test analysis and or
modification to the Detailed Test Plan.
 The test regions or test environment are not available (for any reason).
 The test regions or test environment suffer performance problems below 50% of their normal
operating capacity, such that a region fix will require substantial re-testing of that function.
 [Document all other suspension/resumption. Make sure the resumption criteria are
unambiguously defined].

<Select from below table only testing level related on this DTP> consider the entry and Exit
criteria reasonable on your project>
3.5.2 Pass/Fail Criteria
The specific pass/fail criteria for the testing at both the test cycle and release level are identifying
in table below. This can include percentage of severity 3 and 4 defects that will be allowed to
migrate between test/production environment and any specific business defined criteria. Identify
information in this part , select only current testing level involve in this DTP.
[Document any specific pass/fail criteria for the testing at both the test cycle and the
overall test activities. This can include percentage of severity 3 and 4 defects that will be
allowed to migrate between test/production regions and any specific business defined
criteria].
Table 7: Entry and Exit criteria of testing level
Testing Level Entry criteria Guideline Exit Criteria Guideline
 Test environment available with latest  U/I/S testing objectives met
UIS testing software build  All outstanding errors
 Updated requirements documents (including documented and assigned a severity level
change requests) agreed with the Vendor manager
 Component designs  All severity critical and high errors corrected or
signed-off with agreed short-term workarounds
 Interface designs (e.g.  Full defect logs from final cycle of testing
message formats/API available for review
protocols) agreed with  Sample test plans/scripts available for review
Architecture team and with dev teams
 Test summary report distributed
 Environment configuration
 Software release packaged and under source
data has been defined and set-up
control
 System, Pre-SIT test exit criteria met  SIT testing objectives met
SIT testing
 Business requirements and specification  All test cases have been executed at least once
documents signed-off (100% execution coverage)
 Test environment available with latest  All outstanding errors
software build deployed documented and assigned a severity level
 Environment configuration agreed with the release management and
data has been defined and set-up vendor management.
 Consolidated release note available  All severity critical and high errors corrected or
with agreed short-term workarounds
 SIT test preparation complete
 SIT testing analysis complete
 SIT risk based schedule agreed by all
parties  Test summary report distributed and approved
 SIT exit criteria met  UAT testing objectives met
UAT testing
 Business requirements signed-off  All test cases have been executed at least once
 Business process maps complete and (100% execution coverage)
signed-off  All outstanding errors
 Training material available documented and assigned a severity level
agreed with management team
 Test environment available with latest
software build deployed  All severity critical and high errors corrected or
have documented workarounds formally agreed
 Environment configuration
with business
data has been defined and set-up
 Test summary report distributed and approved
 Formal UAT Sign-off from K-Bank received
 
 

4 Test Conditions
4.1 Business Event 1- BR001
Testing will demonstrate the following:
4.2 Business Event 2 – BR002

4.3 Business Event 14 – BR0014

There is any financial transaction from dormant account. The dormant account means the
account does not have any movement from customer action after end of the first due for 365
days. This excludes all batch jobs i.e. interest posting.
Product Start Date Due Date Open A/C / Sub A/C

3 Month 1/1/2013 31/3/2013 90 (1)
3 Month 1/4/2013 30/6/2013 90 (2)
3 Month 1/7/2013 30/9/2013 90 (3)
3 Month 1/10/2013 31/12/2013 90 (4)
3 Month 1/1/2014 31/3/2014 90 (5)
3 Month 1/4/2014 30/6/2014 90 (6)
The first due of 3-Month fixed account (1), 31/3/2013 + 365 days = 31/3/2014
If there is no customer transaction within 31/3/2014, this 3-Month fixed account is called
dormant account.
Application Name: S1-ET, CT-Win

5 Test Environments
List and/or graphically show the proposed testing environment/s. For small testing projects
complete all of the listed sections. Larger projects may require a separate Test Environment Plan
to be produced. If Master test plan already specify may refer to MTP plan instead.
5.1 Client Side Infrastructure

Provide detailed list/s of required hardware and software at Client side to support testing activity
of each test level and test environment. May use tabular format for explain the content.
5.2 Host/Server Side Infrastructure

Provide detailed list/s of required hardware and software at Host or Server to support testing
activity of each test level and test environment. May use tabular format for explain the content.
5.3 Middleware
Provide detailed list/s of required Middleware to support testing activity of each test level and test
environment. Eg. Test engine or test stub required for interface test.
5.4 Test Data preparation

Define the data subset/s that needs to be pre-loaded into the test environments. This content in
is mention about infrastructure preparation view, it does not about the data condition or concept
that mention in section 3.2 Data test.
[Provide detailed data requirements. Where specific data is required to establish a data
condition or execute a test script provide either a list of these data requirements or
reference the location of this information. Include the processes that will be used to
deliver the data to the test region. (production extract by operations staff, build by
automated scripts, generated by the development team/vendor etc)].

6 Test Schedule
[Provide a schedule showing how testing will be divided for execution. Use the following
as an indicative sample. If a separate schedule is used provide an appropriate docref: and
link and reference the rules governing its management].
Batch Run # Function to be Executed Cycle Date Req

Batch Run 1  Account Enquiries NIL
(Daily)  New Account Set-up
 Transaction Processing
Batch Run 2  Interest Posting 12/06/09
(Cycle)  Minimum Payment
Batch Run 3  Interest Accrual NIL
(Daily)

Appendix A - System Schematic/s

Clearly document the System Schematic used for test on this level.

Test Plan

Uploaded by

Copyright:

Available Formats

Test Plan

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Test Plan

Uploaded by

Copyright:

Available Formats

What is the purpose of this document?

What is the purpose of this document?

What are the different sections covered in this document?

What are the different sections covered in this document?

Reserve bank

Detailed Test Plan - UIS

This copy printed on: July 16, 2019

Document1 (Revision 6) Page 2 of 15

XYZ BANK Confidential

Document1 (Revision 6) Page 3 of 15

XYZ BANK Confidential

Table 3: Reference .......................................................................................................... 6

Document1 (Revision 6) Page 4 of 15

XYZ BANK Confidential

Target is to concentrate on internal and external fraud detection. The primary

1.2 Testing Objectives

1.3 Document Audience

Role Name Email/ Telephone Organization

Document1 (Revision 6) Page 5 of 15

XYZ BANK Confidential

Document Name Author Version Update date

1.5 Definition and Acronyms

Document1 (Revision 6) Page 6 of 15

XYZ BANK Confidential

1. Perform investigations based on business rule.

2.1.1 Functional Scope

2.1.2 Non Functional Scope

Table 4: Non Functional

Non Functional Description

Document1 (Revision 6) Page 7 of 15

XYZ BANK Confidential

1 <High level describe the item of out scope>

2.3 Testing Exclusions

Document1 (Revision 6) Page 8 of 15

XYZ BANK Confidential

3 Detailed Test Approach

3.1 Naming Conventions for Function Groups and Functions

Rename this section as required:

3.2 Test Case Design

3.3 Test Scheduling

Document1 (Revision 6) Page 9 of 15

XYZ BANK Confidential

Figures 1: Test schedule

Table 6: Example test cycle

Batch Run # Function to be Executed Cycle Date

3.4 Data Build

Document1 (Revision 6) Page 10 of 15

XYZ BANK Confidential

Document1 (Revision 6) Page 11 of 15

XYZ BANK Confidential

4.2 Business Event 2 – BR002

4.3 Business Event 14 – BR0014

Product Start Date Due Date Open A/C / Sub A/C

Application Name: S1-ET, CT-Win

Document1 (Revision 6) Page 12 of 15

XYZ BANK Confidential

5.1 Client Side Infrastructure

5.2 Host/Server Side Infrastructure

5.4 Test Data preparation