TEST PLAN

Test Plan

Page 1 of 9 14-11-2019
 TEST PLAN

Document History
Author Version Date Summary of Changes
Karomatul Ummah 1.0 November 14th, 2019 Initial Release

Page 2 of 9 14-11-2019
 TEST PLAN

Date]

Type Position]

Page 3 of 9 14-11-2019
 TEST PLAN

Table of Contents
Document History..........................................................................................................................................2
Table of Contents...........................................................................................................................................4
1. Introduction............................................................................................................................................5
1.1. Purpose................................................................................................................................................5
1.2. Scope...................................................................................................................................................5
1.3. Intended Audience..............................................................................................................................5
1.4. Document Terminology and Acronyms..............................................................................................5
1.5. Reference............................................................................................................................................5
2. Quality Goals..........................................................................................................................................6
2.1. Test Lifecycle......................................................................................................................................6
2.2. Features to Be Tested..........................................................................................................................6
2.3. Features Not to Be Tested...................................................................................................................6
2.4. Functionality to Be Covered...............................................................................................................7
2.4.1. Functionality.....................................................................................................................................7
2.4.2. Reliability..........................................................................................................................................7
2.4.3. Security.............................................................................................................................................7
2.4.4. Capability..........................................................................................................................................7
3. Product Risk Assessment........................................................................................................................7
4. Test Approach.........................................................................................................................................7
4.1. Applicable Testing Types and Techniques.........................................................................................7
5. Entry and Exit Criteria for Test..............................................................................................................8
6. Suspension and Resumptions Criteria....................................................................................................8
7. Test Environment...................................................................................................................................8
7.1. Base System Hardware and Software Platform..................................................................................8
8. Deliverables/Artifacts.............................................................................................................................8
9. Testing Tasks and Schedule...................................................................................................................9
10. Organizational Structure Chart...............................................................................................................9
11. Responsibilities, Staffing, and Training Needs......................................................................................9

Page of 14-11-2019

1 2 3
 TEST PLAN

1. Introduction
1.1. Purpose
This document describes how the application will be tested. Application to be examined is Web UI for
Teller & Funding Products. This document aims to support the creation of Web UI for Teller &
Funding Products application, including:
1. Identify the components of the application that could be tested.
2. Create a list of suggestion for the application as a future reference.
3. Describe the testing strategies to be performed.

1.2. Scope
This document only talks about testing of applications being built. The scope of testing to be tested
include manually.

1.3. Intended Audience

- QA Technical Consultant
- Development Team
- SCM Team
- Project Manager

1.4. Document Terminology and Acronyms

No document terminology and acronym used in this project.

1.5. Reference
– Funding & Teller project Business Requirement Document.
(www.gtddshs.com)

Page 5 of 9 14-11-2019

1 2 3
 TEST PLAN

2. Quality Goals
2.1. Test Lifecycle
Test lifecycle used in this project is Agile Testing approach. The stages is:
1. Create test plan
2. Create test scenario and test case for each task on– Funding & Teller project
3. Execute each test case on Web UI Funding & Teller with manual testing
4. Automation testing Web UI Funding & Teller using Katalon

2.2. Features to Be Tested

This project will cover features such as:
1. Account module
a. Opening account
b. Closing account
c. Block/unblock normal account
d. Block/unblock DTTOT account
e. Override account interest, transactions, and charges
f. Opening account authorization
g. Closing account authorization
2. Transaction module
a. Cash Deposit Transaction
b. Cash Withdrawal Transaction
c. Transfer Transaction
d. Reversal Transaction
e. Transaction Authorization
3. Teller module
a. Denomination Parameter
a. Vault Parameter
b. Teller Account
c. Teller Parameter Authorization
d. Teller transaction, such as:
i. Send Vault by Head Teller
ii. Receive/reject Vault by Teller
iii. Return Cash to Vault by Teller
iv. Receive/reject Cash by Head Teller
v. Teller exchanges
vi. Difference less/more transaction

2.3. Features Not to Be Tested

The feature that will not be tested in this project:
1. Term Deposit feature
2. Performance testing in back end application
3. API/Web services aspect of the application

Page 6 of 9 14-11-2019

1 2 3
 TEST PLAN

2.4. Functionality to Be Covered

End to end Web UI for Teller & Funding poducts.

2.4.1. Functionality
Function on application can receive request and give response

2.4.2. Reliability
Ensure the reliability aspect of the application

2.4.3. Security
The Security aspect for this project is not in the scope defined by Product Owner

2.4.4. Capability
The Capability aspect for this project is not in the scope defined by Product Owner

3. Product Risk Assessment

System function that are crucial for testing are the Web UI Funding & Teller.

4. Test Approach
4.1. Applicable Testing Types and Techniques
1. Test Objective
- Function on application (all menu that required to input data) can input data to be processed
- All request available to the web service can be used in accordance with the system function
2. Technique
- Test each request on each feature
- Test the request with various conditions
- Ensuring the result of the report in accordance with input and data
3. Completion Criteria
- In the input menu, the data can be saved in the database and displays the success message
afterwards
- Request can produce output in accordance with its function
- Error messages appears when any user input non-valid data
- Report produced as expected
- No misspelled word on the response
4. Special Consideration
- There are some unsupported features for Automation Test like: random text/number assertion,
data comparison with database, One Time Password (OTP) and notification (SMS/email)

Page 7 of 9 14-11-2019

1 2 3
 TEST PLAN

5. Entry and Exit Criteria for Test

These are the entry criteria for testing:
- Application is available and ready to be tested
- Test environment is ready and available for testing
- Test personnel is ready and available for testing
These are the exit criteria for testing:
- No major or minor bugs is found from the application
- Test environment is not available
- Project Manager decided to exit the testing process

6. Suspension and Resumptions Criteria

The testing process can be suspended when:
- The application environment is not valid because of not updated database
- The developer team want to refactor and redesign the application code

The testing process will resume when the environment is ready for testing

7. Test Environment
7.1. Base System Hardware and Software Platform
Operating System : Windows 10 Home 64-bit
System Manufacturer : ASUS
System Model : ZenBook UX433FN
Processor : Intel(R) Core(TM) i7-8565U
Memory : 16GB RAM
Tools : Google Chrome, Snagit, Katalon Studio, DBeaver
Database : Postgre

8. Deliverables/Artifacts
These are the document for the testing:
- Test Plan
- Test Scenario
- Test Case
- Test Script
- Test Result

Page 8 of 9 14-11-2019

1 2 3
 TEST PLAN

9. Testing Tasks and Schedule

Testing Task Deliverables Tester Time frame
Create Test Plan Test Plan Anisa 11/15/2019
Develop Test Scenario, Test Scenario, Test
Test Case, Test Script, and Case, Test Script,
Test Result on Redmine and Test Result
dea 11/15/2019 – 20/12/2019
Test Case, Test
Develop automation
Suite, Test Suite
testing via Katalon Studio
Collection

10.Organizational Structure Chart

Project Manager
Rahajeng Iga Titisari

Product Owner
1. Donny
2. Lovely Pomala

Developer
1. Rahmat Riswanto (Team Lead)
DevOps 2. David Design UI/UX
1. Handika Suhandiana 3. Dennis Justine 1. Rheinita Choirun Nikmah
4. Fatan Aminullah
5. M. Kholik Kurniasandy

11.Responsibilities, Staffing, and Training Needs

Role Resources Responsibilities
Functional tester Anisa Automation testing,
Teo Perform black box/functional test
dia

Page 9 of 9 14-11-2019

1 2 3