Oe2 Doc 20110915 Test Plan

7/25/2019 Oe2 Doc 20110915 Test Plan

1/16

TRG Enclave (a division of TRG International)127 Huynh Thuc Khang, Hai Chau, Danang, Vietnam

Tel: +84(511) 625 !!! " #a$: (!511) 625 222

ONLINE EXAM VERSION 2.0

TEST PLAN

Revision: PA1

Enclave% &''h*e Deelment Cente* -age 1 ' 16

7/25/2019 Oe2 Doc 20110915 Test Plan

2/16


Tel: +84(511) 625 !!! " #a$: (!511) 625 222

Revision History

Date Version Description Author ApprovedSep-15-2011 PA1 First Release Lien T. VO N/A

www.enclaveIT.com


7/25/2019 Oe2 Doc 20110915 Test Plan

3/16


Tel: +84(511) 625 !!! " #a$: (!511) 625 222

1. Introduction

The purpose of the Test Plan is to define, schedule and monitor the test execution. It supports thefollowing objectives:

Provide a high level list of the major target test functions.

List the requirements for testing.

Describe the testing strategies to be employed on each target test functions.

Identify the required resources and schedule the Test execution

1.1. Overview of Online Exam version 2.0OE2 is a web application upgraded from previous version with the following additional functions:

Admin can export test with sounds and images

Manage team function

Send exam result to users email after he/she finished an exam

Learner can view their own improvement report

Learner can export exam result report to pdf

Statistics box: top 5 leaners score; display how many user online; total questions

on database

Change GUI for exam page

Change way to choose practice and study test by tree-view

1.2. Scope

1.2.1. In Scope

TheOE2Test Plan defines the integration, system testing approach. The test scope includes thefollowing:

Testing 8 functions.

Quality requirements.

1.2.2. Out of Scope

The following are considered out of scope for OE2Test Plan and testing scope:

Testing performance for 100-200 users at the same time

Enclave% &''h*e Deelment Cente* -age ' 16

7/25/2019 Oe2 Doc 20110915 Test Plan

4/16


Tel: +84(511) 625 !!! " #a$: (!511) 625 222

1.3Assumptions for Test Execution

Software will be delivered on time.

Software is of the required quality.

All service agreements will be met.

All documentation will be up to date.

All bugs found in a version of the software will be fixed and unit tested by the

development team before the next version is released.

For Integration testing, the Developer has completed Unit test carefully.

1.4. Document Terminology and Acronyms

TERM/ACRONYM DEFINITION

OE2 Online Exam version 2.0

N/A Not Applicable

GUI Graphical User Interface

1.5. ReferencesThere will be several formal review points before and during testing. This is a vital element in

achieving a quality product.

Project Schedule

OE2-DOC-SRS-110909 Version 1.0.doc

OE2-DOC-DDD-110922-Version 1.0

Bugzilla's Testing Pages:http://ednaws_024/

http://ednaws_024/http://ednaws_024/

7/25/2019 Oe2 Doc 20110915 Test Plan

5/16


Tel: +84(511) 625 !!! " #a$: (!511) 625 222

2. Test Methodology

2.1. Strategies

Admin generate some tests and export it. If system can export and there are sound

files, answer sheet and blank sheet then the test pass successfully.

Admin create/edit/delete team, or add users into team. If team is

created/edited/deleted or user is added into team then the test pass successfully.

Admin create exam, make schedule for it with users will take exam. After they

finished exam, system will send exam result via email. If users receive their email

with attached file and right content then the test pass successfully. Learner choose year to view their own improvement. At here, they can export it. If

system can export and display the same information with webpage then the test

pass successfully.

Admin imports some new questions, some user online and there are top 5 scores

exist. If system displays this information at the home page then the tests pass

successfully.

Admin creates new structure, make schedule for exam. If the exam page display

with right structure, questions and user can do exam then the test pass successfully.

Learner choose test for practicing and studying. If learner can choose it and take

test then the test pass successfully.


7/25/2019 Oe2 Doc 20110915 Test Plan

6/16


Tel: +84(511) 625 !!! " #a$: (!511) 625 222

3.Target Test Areas

In this release, we will test following functions:

Export test with sounds, answer sheet and blank sheet

Manage team

Send exam result to users email

Export improvement report

Export exam result report

Statistics box

Exam page

Practice and study test page


7/25/2019 Oe2 Doc 20110915 Test Plan

7/16


Tel: +84(511) 625 !!! " #a$: (!511) 625 222

3.1Test Deliverables

Testing will provide specific deliverables during the project. These deliverables fall into threebasic categories: Documents, Test Cases / Bug Write-ups, and Reports. Here is a diagram

indicating the dependencies of the various deliverables. The following page contains a matrix

depicting all of the deliverables that Testing will use.

3.2. Deliverables MatrixThis matrix should be updated routinely throughout the project development cycle in Test

Plan.

DeliverableDocuments

Test Plan

Test Schedule

Test Case / Bug Write-Ups

Test Cases / Results

BugZilla for bug reporting

Reports

Test results report

Test Final Report - Sign-Off

3.3. Documents

3.3.1. Test Plan

The Test Plan is derived from the Requirements, Functional Specifications. The Test Plan

identifies the details of the test approach, identifying the associated test case areas within the

specific product for this release cycle.

3.3.2. Test ScheduleThe Test Schedule is the responsibility of the QC Lead and will be based on information from

the Project Scheduler (done by Project Manager). The project specific Test Schedule may be done in

Project Management (Microsoft Office).

3.3.3. Requirements Traceability Matrix

A Requirements Traceability Matrix (RTM) which is used to link the test scenarios to the

requirements and use cases is a required part of the Test Plan documentation for all projects.

Requirements traceability is defined as the ability to describe and follow the life of a requirement,

in both a forward and backward direction (i.e. from its origins, through its development and

specification, to its subsequent deployment and use, and through periods of ongoing refinement

and iteration in any of these phases).


7/25/2019 Oe2 Doc 20110915 Test Plan

8/16


Tel: +84(511) 625 !!! " #a$: (!511) 625 222

3.4. Defect Tracking & DebuggingALL defects should be logged using BugZilla, to address and debug defects. Developers will

update the defect list on BugZilla and notify QC who request that defect after the defect has beenresolved.

Debugging should be based on Priority High > Medium > Low, these priorities are based on

how critical is the test script in terms of dependency and mainly based on use case scenario.

AllHigh prioritydefects should be addressed within 1 day of the request and resolved/closed

within 2 days of the initial request

AllMedium prioritydefects should be addressed within 2 days of the request and

resolved/closed within 3 days of the initial request

AllLow prioritydefects should be resolved/closed no later than 5 days of the initial request.

3.5. ReportsThe QC Lead will be responsible for writing and disseminating the following reports to

appropriate project personnel as required.

3.5.1. Testing status reports

A weekly status report will be provided by the QC Lead to project personnel. This report will

summarize weekly testing activities, issues, risks, bug counts, test case coverage, and other

relevant metrics.

3.5.2. Phase Completion Reports

When each phase of testing is completed, the QC Lead will distribute a Phase Completion

Report to the Project manager, Development Lead for review and sign-off.

The below bullets illustrates an example of what the document may include.

The document must contain the following metrics:

Total Test Cases, Number Executed, Number Passes / Fails, Number Yet to

Execute

Number of Bugs Found to Date, Number Resolved, and Number still Open

Breakdown of Bugs by Severity / Priority Matrix

Discussion of Unresolved Risks

Discussion of Schedule Progress

3.5.3. Test Final Report - Sign-Off

A Final Test Report will be issued by the QC Lead. It will certify as to the extent to which

testing has actually completed (test case coverage report suggested), and an assessment of the

products readiness for Release to Production.


7/25/2019 Oe2 Doc 20110915 Test Plan

9/16


Tel: +84(511) 625 !!! " #a$: (!511) 625 222

3.6. Bug severity

Level Items Descriptions

1 Critical System crash, performance issues, lost of data

2 Major Functionality failure, misbehavior, incorrect representation

3 Minor Irritants, functionality achieved through workarounds, usability, UI related

4 Cosmetic Spelling and grammar mistakes, font inconsistency

Enclave% &''h*e Deelment Cente* -age . ' 16

7/25/2019 Oe2 Doc 20110915 Test Plan

10/16


Tel: +84(511) 625 !!! " #a$: (!511) 625 222

4. Milestones

(Will be updated after got Project Schedule)

Milestones Start Date End Date

Enclave% &''h*e Deelment Cente* -age 1! ' 16

7/25/2019 Oe2 Doc 20110915 Test Plan

11/16


Tel: +84(511) 625 !!! " #a$: (!511) 625 222

5.Test Cycle Entry and Exit Criteria

5.1. Entry CriteriaFirst Build successful implementation: after implementing and doing unit test.

All developed code must be unit tested.

Test plans must be signed off by Management team and QC Lead.

All human resources must be assigned and in place.

All test hardware and environments must be in place, and free for testing.

5.2. Exit Criteria With all test items, the test will be successful when exit criteria are happened.

Exit criteria: 100% Test cases passed.

Refer to Project Plan, Quality Plan and Acceptance Criteria.

5.3. Abnormal Termination

The source code has too many bugs and cannot run.

The work flow is not the same with the design.

5.4. Resumption CriteriaIn the event that system testing is suspended resumption criteria will be specified and testing

will not re-commence until the software reaches these criteria.


7/25/2019 Oe2 Doc 20110915 Test Plan

12/16


Tel: +84(511) 625 !!! " #a$: (!511) 625 222

6. Environmental Needs

Resource Configuration Installed OS, Software

Hardware Server with static IP

Personal PC Intel Core Duo CPU

or higher, 1 GB or higher

of RAM

Software BugZilla

IE browser


7/25/2019 Oe2 Doc 20110915 Test Plan

13/16


Tel: +84(511) 625 !!! " #a$: (!511) 625 222

7. Roles and Responsibilities

7.1. Management team

Project Manager/QA Leader Lien T. VO

Ensure OE2 is delivered to schedule, budget & quality

Ensure Exit Criteria are achieved prior to sign off testing

Regularly review Testing progress with QC Leader role

Raise and manage issues/risks relating to project

Review & sign off Test approach, plans and schedule


7/25/2019 Oe2 Doc 20110915 Test Plan

14/16


Tel: +84(511) 625 !!! " #a$: (!511) 625 222

7.2. Development Team

Development leader Dai N. UNG

Review high level / detailed test plans

Resolve design issues

Resolve development issues

Support user acceptance testing

Development team Dai N. UNG, Hoang V. NGUYEN, Bich-Lieu T. TRAN, Khuyen T.NGUYEN, Thanh-Thao T. NGUYEN

Develop Unit test scripts

Make Unit test

Fix bugs


7/25/2019 Oe2 Doc 20110915 Test Plan

15/16


Tel: +84(511) 625 !!! " #a$: (!511) 625 222

8.Risks and Contingency

Risk Mitigation Strategy Contingency (Risk is realized)

Delay of the design PM and Developer teams Leader must

tracking members to complete on time.

Over time, request to support

Delay of the

implementation

PM and Developer teams Leader must



The source code has

too many bugs

PM and Developer teams Leader must



The design has

problems and must

change so that must

spend time to edit

test cases.

Design team must announce soon to QC

team when has anything change in the

design.



7/25/2019 Oe2 Doc 20110915 Test Plan

16/16


Tel: +84(511) 625 !!! " #a$: (!511) 625 222

9. Sign off

This document must be formally approved before testing. The following people will be

required to sign off:

Management Team: Lien T. VO, Dai N. UNG