1. www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165

2. www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
Test Plan – Cyclos

3. www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
Table of Contents
1. Introduction..........................................................................................................................................................4
2. Scope of Testing for the Project...........................................................................................................................4
2.1 Features..................................................................................................................................................4
3. Application Details...............................................................................................................................................5
3.1 Technology Details ....................................................................................................................................5
4. Test Approach ......................................................................................................................................................5
4.1 Types of Tests to be conducted ..................................................................................................................5
4.2 Traceability Matrix.....................................................................................................................................6
4.3 Test Case Preparation Approach ...............................................................................................................7
Test Case Development....................................................................................................................................7
4.4 Test Execution Process..............................................................................................................................7
4.4.1 Pass/ fail criteria......................................................................................................................................7
4.4.2 Suspension and Resumption Criteria......................................................................................................8
4.5 Defect Management..................................................................................................................................8
Defect reporting (Excel Template)...........................................................................................................8
5. Test Effort and Schedule......................................................................................................................................9
5.1 Test Effort..................................................................................................................................................9
5.2Test Schedule ..............................................................................................................................................9
6. Test Environment .................................................................................................................................................9
Following are the Test Environment..............................................................................................................10
6.1 Hardware Environment...........................................................................................................................10
6.2 Software Environment ............................................................................................................................10
6.3 Test Tools .................................................................................................................................................10
7. Staffing and Training needs ...............................................................................................................................11
8. Communication Plan – Roles and Responsibilities (RACI)..............................................................................11
9. Assumptions, Risks and Dependencies..............................................................................................................11
10. Quality Assurance Approach............................................................................................................................12
11. Skill Gap Analysis............................................................................................................................................12
12. Escalation Approach ........................................................................................................................................13
13. Acceptance and Sign-off Criteria.....................................................................................................................13
14. Artifacts............................................................................................................................................................13
15. Test Status Reporting .......................................................................................................................................13
16. Test metrics ......................................................................................................................................................13

4. www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
1. Introduction
The purpose of this Test Plan is to outline the test approach which includes objective, scope, approach, schedule and risks.
Cyclos is a project of STRO, a leading organization on monetary innovations. Cyclos offers a complete on-line payment
system with additional modules such as e-commerce and communication tools. The Cyclos platform permits institutions
such as local banks and MFI`s to offer banking services that can stimulate local trade and development. Cyclos is also
used by many organizations and communities to provide community currency services.
With the latest version it is possible to roll out mobile banking services such as SMS banking and apps for smart phones.
Cyclos is published under the GPL (open source) license meaning that it can be downloaded for free and used at no cost.
Cyclos is currently available in ten languages and new languages are added with each release.
2. Scope of Testing for the Project
The following table defines In Scope and Out of Scope of testing for Cyclos application.
Cyclos application Scope/out of Scope
In Scope Out of Scope
» Functionality Testing
» UI Testing
» Compatibility testing
» Usability testing
» Performance Testing
» Accessibility testing
» Configuration testing
» Compliance testing
» Interoperability testing
2.1 Features
Cyclos application supports the following features:
» Account Information
» Schedule Payments
» Invoices
» Loans
» Member Payment
» System Payment
» Request Payment by SMS

5. www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
» Member Invoice
» Profile
There are few more features which are kept out of scope for current build testing. They will be part of the next upcoming
builds.
3. Application Details
Using Cyclos application, users can view the account information, scheduled payments, invoices, loan info, Payments,
Preferences and Profile information
3.1 Technology Details
The application is an Android application which provides parental control and protection on child’s phone.
» Supported OS: Windows 2003 & above
» Front End: Ajax
» Web Server: Apache
» Database: MySQL
» Language: English
4. Test Approach
Document defines the overall approach for test cases authoring, test execution conducted on multiple types of testing and
defect management process established for this project
4.1 Types of Tests to be conducted
Smoke Testing:
Smoke is a build verification test. The principle of this testing is to decide if a build is stable enough to proceed with
functional testing.
Entry criteria:
» Requirements baseline
» Test environment set up
» Build released with build release notes on the features to be tested for that build
Exit criteria:
» All test cases are authored and executed
» All critical and high severity defects are closed

6. www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
Functional/UI Testing:
Functional testing is carried out to verify the various functionalities are performing as expected
Cyclos application functionality includes:
» All the features mentioned above
Entry criteria:
» Business requirement should be baseline
» Test Environment should be ready for QA to test
» Test cases should be authored, reviewed and approved
» Application ready to test for QA
Exit criteria:
» All test cases are authored and executed
» All critical and high severity defects are closed
Integration Testing:
After the installation of Cyclos application, Integration testing will be done between the web application and the mobile
application.
Entry criteria:
» Business requirement should be baseline
» Test Environment should be ready for QA to test
» Test cases should be authored, reviewed and approved
» Application ready to test for QA
Exit criteria:
» All test cases are authored and executed
» All critical and high severity defects are closed
4.2 Traceability Matrix
Traceability Matrix ensures Test Coverage. It traces the deliverable's by establishing the thread from each requirement -
test cases and then defects, from project initiation to final implementation.

7. www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
4.3 Test Case Preparation Approach
Test Case Development
» Test cases will be written for the features in scope
» The test cases will be reviewed internally and base-lined
» The reviews will take place at different levels – at Peer level initially and detailed later
» Test cases will be sent across to client POC for final review and sign off
4.4 Test Execution Process
» Test cases will be written in Ms Excel for the features in scope
» After the test cases are approved and signed off by client POC test cases will be executed and the execution
results will be shared on daily basis with the stakeholders
4.4.1 Pass/ fail criteria
» Pass Criteria: Test Case(s) results matching with the expected results
» Fail Criteria: Test Case(s) results not matching with the expected results

8. www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
4.4.2 Suspension and Resumption Criteria
If the number of defects and the type of defects are very high in volume in the beginning of the application testing, it’s
advisable to suspend the testing activity as this is considered to be poor quality of coding. Such applications are
returned to the developers to fix the issues and release a new build so that quality testing activities can be resumed.
4.5 Defect Management
Defect reporting (Excel Template)
Excel template will be used to address the defects and the testers are advised to send a daily defect report to all the
stakeholders. Developers will be updating the defect report and the update will be sent to the concerned test team after
resolving the issues. Debugging will be based on Priority – High > Medium > Low. These priorities are set by the testers
on the level of criticalities and in terms of dependency.
All High priority defects should be addressed within 1 day of the request and resolved/closed within 2 days of the initial
request
All Medium priority defects should be addressed within 2 days of the request and resolved/closed within 4 days of the
initial request
All Low priority defects should be resolved / closed no later than 5 days of the initial request
Severity ID Severity
Level
Severity Description
1 Critical Complete loss of core functionality which impacts on core functionality
like, show stopper2 High High Impact on the functionality, an effective and imminent work
around and resolution available for this functionality
3 Medium Average impact on the functionalities
4 Trivial Minor impact on the functionalities
Priority IDPriority Level Priority Description
1 Must Fix This bug must be fixed immediately; the product cannot ship with
these defects2 Should Fix These are important problems that should be fixed at the earliest
3 Important Decision will be made during the defect triage meet
4 Low Priority Decision will be made during the defect triage meet
Following is the SLA for defect management:
SNO SEVERITY TURNAORUND TIME (in Hrs)
1 CRITICAL 24
2 HIGH 48
3 MEDIUM >48

9. www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
5. Test Effort and Schedule
5.1 Test Effort
This project life is of 3 weeks and following are the activities that will be performed:
» Analyze the application
» Identify the requirements for functional/smoke testing
» Identify the test data requirements and carrier priorities
» Develop Test plan and strategy
» Strengthen existing test cases and author additional test cases as required
» Build detailed test plans for testing
» Build dashboard report
» Conduct functional/smoke testing
» Identify and log defects
» Conduct defect triage meetings
» Perform defect trend analysis
» Publish reports
5.2 Test Schedule
S.No Phase Tasks Start Date End Date Deliverables
1.a Test Plan Creating test plan
DD-June-
YY
DD-June-
YY
Test Plan
1.b Test Case Authoring Test Case Creation
DD-June-
YY
DD-July-
YY Test Cases in Ms Excel
2.a Test Case Execution Test Case Execution
DD-June-
YY
DD-July-
YY
Test Cases Execution
Results and
Defect Report
6. Test Environment

10. www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
Following are the Test Environment
6.1 Hardware Environment
--TBD--
6.2 Software Environment
Internet Explorer (8.x) and (9.x)
Mozilla Firefox 13.x and above
Chrome 19.x and above
Supported OS: Windows 2003 & above
6.3 Test Tools
Tool Name Purpose
MS Excel 2007 It will be used for documenting test cases authoring, Defect Tracking
MS Word Test Plan

11. www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
7. Staffing and Training needs
--TBD--
[The purpose of this section is to describe the training(s) required for Training on the application/system and any
test tools to be used]
8. Communication Plan – Roles and Responsibilities (RACI)
» Daily Reports on the Status of the project will be communicated on the deliverables published
» Weekly meeting with the client POC
» Issues, dependencies and risks will be bought in attention to the client POC
9. Assumptions, Risks and Dependencies
Assumptions
» Testing would be conducted only on one build. In case there are any plans to release more builds for testing, H2K
requests to intimate prior for understanding the changes and undertaking appropriate actions.
» All relevant test equipment required for testing would be made by H2K.
Risks
Risk Management template to be added

12. www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
Dependencies
» Information needed for the queries which H2K Team has with respect to application to be provided at the earliest.
10. Quality Assurance Approach
Following is the approach for reviewing test artifacts
9.1 Test Deliverables
S.No Document Review1 Review 2 Review & Approved
1. Test Plan Lead Test manager xxxx
2. Test Cases Peers, lead Test manager xxxx
3. Test Execution Report Lead Test manager xxxx
9.2 Service Delivery Review
S.No Document Review conducted by @ H2K Reference Document
1. Service Delivery Review 1 Delivery Manager “XLS as attachment”
2. Service Delivery Review 2 Senior Vice President - Delivery “XLS as attachment”
9.3 Knowledge Management
» Knowledge Acquisitions
» Knowledge Dissemination
» Knowledge Archival
11. Skill Gap Analysis
--TBD--
[The purpose of this section is to continuously track the competency levels of team’s present knowledge, identify
gaps, bridge the gaps and enrich knowledge and skills to become master in the skills required for the project]

13. www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
12. Escalation Approach
Role Email Cell/Landline
Test Manager xxxx@h2k.com Applicable
Delivery Manager abc@h2k.com Applicable
13. Acceptance and Sign-off Criteria
User acceptance is acceptable quality after testing the products.
» Ensure critical functional requirements are working as expected
» Contain specific pass or fail criteria
» Address all aspects of the system in detail
» All the severity defects have been fixed and closed
» Identify unacceptable errors
14. Artifacts
» Access to client’s QA environment
» Functional documents
15. Test Status Reporting
» Daily Status
» Weekly Status
» Test Cases Authored Spreadsheet
» Test Execution report
» Defect report
16. Test metrics
» Test Case Productivity
» Defect Productivity
» Defect Trend
» Defect Severity
» Defect Distribution, module wise

14. www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
www.H2KINFOSYS.com || Training@H2KInfosys.com || H2KInfosys@Gmail.com
USA: +1-770-777-1269 || UK: +44-0203-371-7165
---------------------------------------------- End of Document -------------------------------------------------