TEST PLAN

Product Name: Kolomoni Digital Banking

Date: 11-03-2024
Table of Contents
Overview....................................................................................................................................2
Scope..........................................................................................................................................2
Inclusions................................................................................................................................2
Test Environments...................................................................................................................2
Exclusions...............................................................................................................................2
Test Strategy..............................................................................................................................3
Defect Reporting Procedure:.....................................................................................................4
Roles/Responsibilities................................................................................................................4
Test Schedule.............................................................................................................................5
Test Deliverables.......................................................................................................................5
Pricing........................................................................................................................................5
Entry and Exit Criteria...............................................................................................................5
Suspension and Resumption Criteria.........................................................................................6
Tools..........................................................................................................................................7
Risks and Mitigations................................................................................................................7
Approvals...................................................................................................................................7
Overview
As part of the project, Capital Sage asked QA Engineer’s to test End to End functionalities of
the “Kolomoni Digital Banking” Mobile application.
This document serves as high level test planning document with details on the scope of the
project, test strategy, test schedule and resource requirements, test deliverables and schedule.

Scope
The scope of the project includes testing the following features of “Kolomoni Digital
Banking “ Mobile application.

Inclusions
• Register
• Login & Logout
• Forgot Password
• Savings
• Intra-Bank Transfer
• Inter-Bank Transfer
• Add Beneficiary
• Loans
• Buy Airtime
• Buy Data
• Pay Electricity Bills
• Pay Cable TV Bills
• Pay Education Bills
• Pay Sports Betting Bills
• Complete Account Setup
• Transaction History Page
• Recent Transaction Table
• Generate Account Statement
• Request for Card
• Account Limit
• Change Transaction Pin
• Reset Transaction Pin
• Change Password
• Dark Mode Option
• Biometrics Option
• Support Page
• Analytics Page
• Fund Account
• Profile Information Page
• Home Page
• Transaction Details Page
• Report Transaction Issues Option
• More Page

From our understanding, we believe above functional areas need to be Tested.

Test Environments
• Andriod – 11,12,13,14
• Andriod Tablets
• IOS
Test Strategy
The QA Engineers have communicated with ‘Capital Sage Holdings’ and has understood that
we need to perform Functional Testing of all the functionalities mentioned in the above
Scope section.
As part of Functional Testing, we will follow the below approach for Testing:
Step 1 – Creation of Test Scenarios and Test Cases for the different features in scope.

 We will apply several Test Designing techniques while creating Test Cases
• Equivalence Class Partition
• Boundary Value Analysis
• Decision Table Testing
• State Transition Testing
• Use Case Testing
 We also use our expertise in creating Test Cases by applying the below:
• Error Guessing
• Exploratory Testing
 We prioritise the Test Cases
Step 2 – Our Testing Process, When We Get An Application For Testing:

 Firstly, we will perform Smoke Testing to check whether the different and important
functionalities of the application are working.
 We reject the build, if the Smoke Testing fails and will wait for the stable build before
performing in depth testing of the application functionalities.
 Once we receive a stable build, which passes Smoke Testing, we perform in depth
testing using the Test Cases created.
 Multiple Test Resources will be testing the same Application on Multiple Supported
Environments simultaneously.
 We then report the bugs in bug tracking tool and send dev. management the defect
found on that day in a status end of the day email.
 As part of the Testing, we will perform the below types of Testing:
• Smoke and Sanity Testing
• Regression Testing & Retesting
• Usability Testing, Functionality
• UI Testing
 We repeat Test Cycles until we get the quality product.
Step 3 – We Will Follow The Below Best Practices To Make Our Testing Better:

 Context Driven Testing: We will be performing Testing as per the context of the
given application.
  Shift Left Testing: We will start testing from the beginning stages of the development
itself, instead of waiting for the stable build.
 Exploratory Testing: Using our expertise we will perform Exploratory Testing, apart
from the normal execution of the Test cases.
 End to End Flow Testing: We will test the end-to-end scenario which involve
multiple functionalities to simulate the end user flows.

Defect Reporting Procedure:

During the test execution:

• Any deviation from expected behaviour by the application will be noted. If it can’t be
reported as a defect, it’d be reported as an observation/issue or posed as a question.
• Any usability issues will also be reported.
• After discovery of a defect, it will be retested to verify reproducibility of the defect.
Screenshots with steps to reproduce are documented.
• Every day, at the end of the test execution, defects encountered will be sent along with
the observations.
Note:

• Defects will be documented in a Google sheets Document.

• Test scenarios and Test cases will be documented in a Google sheets document.

Roles/Responsibilities
Name Role Responsibilities
Adeniran Bukola Test  Escalations
Manager
Adeniran Bukola Test Lead  Create the Test Plan and get the client
signoffs
 Interact with the application, create and
execute the test cases
 Report defects
 Coordinate the test execution. Verify
validity of the defects being reported.
 Submit daily issue updates and summary
defect reports to the client.
 Attend any meeting with Stake Holders.
Adeniran Bukola Senior Test  Interact with the application
Engineer  Create and Execute the Test cases. ✓
Report defects
Adeniran Bukola Test  Interact with the application
Alelumhe Zion Engineer  Execute the Test cases.
 Report defects
Test Schedule
Following is the test schedule planned for the project:
Task Time Duration

▪ Creating Test Plan 11-03-2024

▪ Test Case Creation 12-03-2024 to 22-03-2024
▪ Test Case Execution 20-03-2024 to 01-04-2024
▪ Summary Reports Submission 02-04-2024

Test Deliverables
The following are to be delivered to the client:
Deliverables Description Target Completion
Date
Test Plan Details on the scope of the Project, test 05-04-2024
strategy, test schedule, resource requirements,
test deliverables and schedule

Functional Test Test Cases created for the scope defined 05-04-2024
Cases
Defect Reports Detailed description of the defects identified 31-04-2024
along with screenshots and steps to reproduce
on a daily basis.
Summary Summary Reports – 10-04-2024
Reports Bugs by Bug#,
Bugs by Functional Area and
Bugs by Priority

Pricing
Not Applicable

Entry and Exit Criteria

The below are the entry and exit criteria for every phase of Software Testing Life Cycle:
Requirement Analysis
Entry Criteria:

• Once the testing team receives the Requirements Documents or details about the
Project
Exit Criteria:
 • List of Requirements are explored and understood by the Testing team
• Doubts are cleared
Test Planning
Entry Criteria:

• Testable Requirements derived from the given Requirements Documents or

Project details
• Doubts are cleared
Exit Criteria:

• Test Plan document (includes Test Strategy) is signed-off by the Test Lead
Entry Criteria:

• Test Plan Document is signed-off by the Test Lead

Exit Criteria:

• Test Scenarios and Test Cases Documents are signed-off by the Client Test
Execution
Entry Criteria:

• Test Scenarios and Test Cases Documents are signed-off by the Test Lead
• Application is ready for Testing
Exit Criteria:

• Test Case Reports, Defect Reports are ready

Test Closure
Entry Criteria:

• Test Case Reports, Defect Reports are ready

Exit Criteria:

• Test Summary Reports

Suspension and Resumption Criteria

Based on the Client decision, we will suspend and resume the Project.
We will ramp up and ramp down the resources as per Client needs.

Tools
The following are the list of Tools we will be using in this Project:

 Google Docs and Sheets

 Post Man
Risks and Mitigations
The following are the list of risks possible and the ways to mitigate them:
Risk: Non-Availability of a Resource
Mitigation: Backup Resource Planning
Risk: No Staging Environment
Mitigation: Test on Production Environment
Risk: Less time for Testing
Mitigation: Ramp up the resources based on the Client needs dynamically

Approvals
Team will send different types of documents for Client Approval like below:

• Test Plan
• Test Scenarios
• Test Cases
• Reports
Testing will only continue to the next steps once these approvals are done.