HTV TEAM
BUILDING FOLK GAME“O AN QUAN” ON
ANDROID PLATFORM
(BFG) PROJECT
Test Plan
Version 1.0
BFG Project
<Iteration/ Master> Test Plan
Trung, Hang
Date
05/03/2012
Confidential
Version
1.0
Version:
1.0
Date: 5/3/2012
Revision History
Description
Author
Initial release
HTV Team, 2016
Page 2
BFG Project
<Iteration/ Master> Test Plan
Trung, Hang
Version:
1.0
Date: 5/3/2012
Table of Contents
1
Introduction
1.1 Purpose
1.2 Scope
1.3 Intended Audience
1.4 Document Terminology and Acronyms
1.5 References
5
5
5
5
5
5
2
Test Strategy
2.1 Unit Testing
2.2 Function Testing
2.3 Integration Testing
2.4 System Testing
2.5 User Interface Testing
2.6 Documentation Testing
2.7 User Acceptance Test
5
5
5
6
6
6
6
6
3
Test Cycles
7
4
Environment Requirement
4.1 Hardware Requirement
4.2 Software Requirement
8
8
8
5
Deliverables
8
6
Human Resources and Responsibilities
6.1 Human Resource
6.2 Role and Responsibilities
9
9
9
7
Assumptions and Risks
7.1 Assumptions
7.2 Risks
Confidential
10
10
10
HTV Team, 2016
Page 3
BFG Project
<Iteration/ Master> Test Plan
Trung, Hang
Version:
1.0
Date: 5/3/2012
Document Approvals: The following signatures are required for approval of this
document.
Huy Nguyen
Mentor 1
Quang
Signal
Date
Duong Nguyen Trinh Trung
Mentor 2,
Customer
Signal
Date
Hang Signal
Date
Quoc Signal
Date
Dang
Thi
Project manager
Dang
Thuy
Hung
Phan
Product Manager
Confidential
HTV Team, 2016
Page 4
BFG Project
<Iteration/ Master> Test Plan
Trung, Hang
Version:
1.0
Date: 5/3/2012
Test Plan
1
Introduction
1.1
Purpose
The overall purpose of testing is to ensure the “O An Quan” application meets all of
its technical, functional and business requirements. The purpose of this document is to
describe the overall test plan and strategy for testing the “O An Quan” application. The
approach described in this document provides the framework for all testing related to this
application.
1.2
Scope
This test plan describes the unit, system integration, and system level tests that will be
performed on components of O An Quan.
1.3
Intended Audience
Tester, coder
1.4
Document Terminology and Acronyms
Terminology/ Acronyms
1.5
2
Description
References
Test Strategy
2.1
Unit Testing
Unit testing is performed by the application developers testing in the development
environment. This testing phase will have a “white box” perspective, which means the
application developers know, and will be testing the internal logical structure of each
software component.
2.2
Function Testing
Functional testing will be performed to verify all functional requirements are met
successfully. This will be accomplished through black box testing.
Confidential
HTV Team, 2016
Page 5
BFG Project
<Iteration/ Master> Test Plan
Trung, Hang
Version:
1.0
Date: 5/3/2012
2.3
Integration Testing
Integration testing will be performed to combine individual modules are combined
and tested as a group. The idea is to test combinations of pieces and eventually expand the
process to test your modules with those of other groups. Eventually all the modules making
up a process are tested together.
2.4
System Testing
The System testing will focus on the behavior of the O An Quan system. User
scenarios will be executed against the system as well as screen mapping and error message
testing. Overall, the system tests will test the integrated system and verify that it meets the
requirements defined in the requirements document.
2.5
User Interface Testing
User Interface (UI) testing verifies a user’s interaction with the software. The goal of
UI testing is to ensure that the UI provides the user with the appropriate access and
navigation through the functions of the target-of-test. In addition, UI testing ensures that the
objects within the UI function as expected and conform to corporate or industry standards.
2.6
Documentation Testing
Tests will be conducted to check the accuracy of the user documentation. These tests
will ensure that no features are missing, and the contents can be easily understood.
2.7
User Acceptance Test
User acceptance testing activities will be performed by the business users. The
purpose of this testing will be to ensure the application meets the users’ expectations.
Confidential
HTV Team, 2016
Page 6
BFG Project
<Iteration/ Master> Test Plan
Trung, Hang
3
Version:
1.0
Date: 5/3/2012
Test Cycles
Status of TEST
UNTESTED
FAIL
PENDING
PASS
Confidential
New feature, not tested
Feature is tested: Error
Feature is corrected, wait for testing again
Feature is tested: Ok
HTV Team, 2016
Page 7
BFG Project
<Iteration/ Master> Test Plan
Trung, Hang
Version:
1.0
Date: 5/3/2012
Error level:
FATAL
Serious
Medium
Cosmetic
4
Environment Requirement
4.1
Hardware Requirement
No.
1.
4.2
Item
PC/Laptop.
Purpose
For team member
use.
Quantity
2
Acceptance Criteria
(optional)
Run Android Platform
2.2 or higher.
Screen Large: 3 inches or
larger.
Software Requirement
No.
Item
Purpose
O An Quan Application under
Application. test.
1.
5
The program shutdown abnormally
Cannot continue running program
Can continue program by another way
Error belongs to interface (Font size, size of
controls...)
Quantity
2
Acceptance Criteria
(optional)
Passed Unit test.
Deliverables
The following artifacts will be testing deliverables, available to the stakeholders.
-
Test Plan.
-
Test Cases.
-
Test Cases Review.
-
Defect Reports.
-
Final Test Summary Report.
Confidential
HTV Team, 2016
Page 8
BFG Project
<Iteration/ Master> Test Plan
Trung, Hang
6
Version:
1.0
Date: 5/3/2012
Human Resources and Responsibilities
6.1
Human Resource
This table shows the staffing assumptions for the test effort. Test team is responsible
for preparing test plan and conducting testing activity.
Member Name
Dang Thi Thuy Hang
Leader
Phan Quoc Hung
Member
Pham Minh Trung
Member
Tran Tan Vu
Member
Nguyen Dang Quang Huy
Mentor 1/ Sponsor
Nguyen Trinh Trung Duong
Mentor 2/ Customer
6.2
Position
Notes
Role and Responsibilities
Resource Type

Sponsor





Project Manager


Confidential
Responsibilities
Provides Go/No Go
authorization that product is
ready for release as part of
implementation planning and
launch process
Prioritizes issues and defects,
and manage technical resources
Makes decisions on unresolved
issues
Provides guidance on the overall
project
Coordinates and develops
project schedule
Liaison with business to ensure
participation and ownership
Tracks all project activities and
resources, ensuring project
remains within scope
Facilitates identifying and
bringing closure to open issues
HTV Team, 2016
Name
Huy Nguyen Dang Quang
Duong Nguyen Trinh Trung
Hang Dang Thi Thuy
Page 9
BFG Project
<Iteration/ Master> Test Plan
Trung, Hang
Version:
1.0
Date: 5/3/2012


Subject Matter
Experts

Developer Team
Lead


Developers




Business Lead


Testers
7

Communicates project status
Define business requirements
and expected results for business
acceptance
Execute user acceptance testing
Design application architecture
Create technical design
Write application code
Resolve defects
Support testers
Write business requirements, test
plan and test cases
Maintain requirements and
defect reporting in Test Director
Lead testing cycle
Perform user acceptance testing
Hang Dang Thi Thuy
Trung Pham Minh
Hung Phan Quoc
Vu Tran Tan
Hang Dang Thi Thuy
Trung Pham Minh
Trung Pham Minh
Vu Tran Tan
Assumptions and Risks
7.1 Assumptions
- The Business team has reviewed and accepted functionality identified in the User
Stories and Breaking Stories into Tasks document.
- Code walkthroughs/reviews will be completed by the development team.
- Unit testing will be completed by the development team prior to release to the test
team.
- Testers will test what is documented in the requirements.
- The test team will have a separate test environment to perform testing.
- All changes to requirements will be communicated to the test team.
- Resources identified in this plan are available to test the application and resolve
defects and address issues as they are raised by the test team.
7.2
Risks
Risk Factor
Misunderstand the
requirements
Probability
2
Impact Priority
3
6
Mitigation Strategy
- Make the requirements
approved by customer.
-
Confidential
HTV Team, 2016
Assign experienced people
to involve in requirement
analysis phase
Page 10
BFG Project
<Iteration/ Master> Test Plan
Trung, Hang
Requirements are
always change
New Tech. & Dev.
Tools
Version:
1.0
Date: 5/3/2012
3
3
3
2
9
6
-
Make the requirements
approved by customer.
Assign experienced people
to involve in requirement
analysis phase
-
Building Demo
-
More working hours for
studying
Consult experts.
-
Fixing bug speed of
developers
3
3
9
-
Working with
Development Leader
usually to lay down bug
fixing time
Aggressive target
date increases the
risk of defects being
migrated to
production. If
development
timelines are not
met, this will directly
impact the testing
timelines.
3
3
9
-
Control and track team’s
activities using time log
daily, encourage team’s
member to complete their
tasks on time following
schedule.
Note:
-
Confidential
Priority = Probability*Impact
Probability of occurrence will be defined clearly as weight : 1-Low, 2-Average, 3-
High, 4-Top.
Impact also will be defined clearly as weight. It depends on which impacted on 1Low, 2- Average, 3- High, 4-Top.
HTV Team, 2016
Page 11