1. Introduction of QA Team............................................................................................................5

1.1 Introduction..........................................................................................................................5

1.2 Contact list............................................................................................................................5

1.3 Organization.........................................................................................................................5

2. Working Process.........................................................................................................................6

2.1 Working process in QA team...............................................................................................6

2.2 Tracking systems:.................................................................................................................6

2.3 Other notes: TBD.................................................................................................................7

3. Products under Test.....................................................................................................................7

3.1 EWallet.................................................................................................................................7

3.1.1 Documents.....................................................................................................................7

3.1.2 Test suite.......................................................................................................................8

3.2 Topup website......................................................................................................................8

3.2.1 Documents.....................................................................................................................8

3.2.2 Test suite.......................................................................................................................9

3.3 Topup SMS...........................................................................................................................9

3.3.1 Documents.....................................................................................................................9

3.3.2 Test suite.......................................................................................................................9

3.4 Taxi payment (Mai Linh taxi)..............................................................................................9

3.4.1 Documents.....................................................................................................................9

3.4.2 Test suite.....................................................................................................................10

3.5 Remittance..........................................................................................................................10

3.5.1 Documents...................................................................................................................10

3.5.2 Test suite.....................................................................................................................10

3.6 MSS....................................................................................................................................10

3.6.1 Documents...................................................................................................................11

3.6.2 Test suite.....................................................................................................................11

4. Guidelines and Templates.........................................................................................................11

4.1 Guidelines...........................................................................................................................11

4.1.1 Using Linux OS...........................................................................................................11

4.1.2 Necessary software to install.......................................................................................11

4.1.3 Setup systems..............................................................................................................12

4.1.4 Using Test tools...........................................................................................................12

4.1.5 Setup automation test..................................................................................................13

4.2 Templates...........................................................................................................................13

4.2.1 Test case......................................................................................................................13

4.2.2 Bug..............................................................................................................................13

5. Others........................................................................................................................................13

5.1 Inventories of team:............................................................................................................13

5.2 Release management..........................................................................................................13

6. Training Schedule.....................................................................................................................13

1. Introduction of QA Team

1.1 Introduction

QA team is responsible for verifying quality of products developed by Engineering team and assuring the quality of released products. Currently, QA team is divided into 2 groups: Internal test group and Integration test group. Internal test group is responsible for verifying the developed builds including

functional test and performance test. The build is tested with simulator of partner system to ensure all functions and their performances work correctly based on the Product Requirements Document from Business team and Specification Document of Development team.

Integration test group is responsible for verifying the integration between our products and partner systems including API test, End to End and Acceptance test for outsourcing products. The build which is used for Integration test is released from Internal test group if it is qualified. Integration test group work directly with client and coordinate with the Operation team to fulfill their tasks.

In the other hand, we have separate teams being responsible for different projects such as MPP, MEP, Bank Admin, Mobivi Admin, MPP mobile app, Topup website, Topupsms, Banktool, Agent, Otpcmd, Mailinh, Bank API, Remittance, Money Transfer Soap, POS, B2B Soap...

1.2 Contact list

Names, dates of birth, phone numbers and yahoo messenger ID’s of all team members are stored in the contact list. It helps the contact between team members as well as to get to know each other easily.Contact list is put on Source Forge at http://10.120.16.16/sf/go/doc1019?nav=1 Notes: New member needs to update his/her information into this file when joining the team.

1.3 Organization

Following is the organization of QA team. It can also be accessed by opening the file on Source Forge at http://10.120.16.16/sf/go/doc1203?nav=1

2. Working Process

2.1 Working process in QA team

Test process defines the workflow of assigning task and reporting result between test members involved in the test cycle. The workflow of test process is put on Source Forge at http://10.120.16.16/sf/go/doc1037?nav=1

Testing and releasing build process defines the cycle of testing build, fixing bugs and releasing builds between QA team and Development team. The workflow of testing and releasing build is put on Source Forge at http://10.120.16.16/sf/go/doc1041?nav=1

Bug Life Cycle defines the cycle of opening, fixing and closing bugs between QA team and Development team. The bug life cycle is put on Source Forge at http://10.120.16.16/sf/go/doc1025?nav=1

Working process between Internal test group and Integration test group defines workflow of releasing build and reporting issue between these two groups. The working process is put on Source Forge at http://10.120.16.16/sf/go/doc1204?nav=1

2.2 Tracking systems:

Source Forge: the centralized location for QA team members to control and manage tasks, documents, test scripts and other miscellaneous. - Source Forge is accessed at http://10.120.16.16/sf/sfmain/do/home - Every member is provided an account to access this system. New member

needs to ask manager to create an account for him/her. - All members need to update status, achievements, issues… of their tasks every

day.- All documents relating to testing is stored on this system. Whenever team

member need to update file, he/she has to download the latest file to update then re-upload the new file.

Mantis: the bug tracking system to report, control and manage bugs. - Mantis is accessed at http://10.120.20.16/mantis/my_view_page.php - Every member is provided an account to access this system. New member

needs to ask manager to create an account for him/her. - When testing, tester needs to file bugs into Mantis and assigns to appropriate

developers as soon as the bug found. The tester is responsible for the bug he/she filed so that he/she needs to re-verify, close or re-open the bug when it is re-assigned to him/her by the developers.

- The guideline of reporting bug is put on Source Forge at http://10.120.16.16/sf/go/doc1064?nav=1

Engineering SVN: The centralized location for developers to control and manage source code. QA engineers are also provided accounts to check out source code to install system under test.- Engineering SVN can be access at your_account@10.120.20.20/data/svn-engr/ - New member needs to ask manager to create an account for him/her.

2.3 Other notes: TBD

3. Products under Test

3.1 EWallet

EWallet is the main product of our company which provides the services of e-payment including services on website, on mobile application and on sms framework. The Ewallet system is constructed with the integration of EWallet , Core Bank of Banks and systems of Merchants.

3.1.1 Documents

All documents relating to EWallet is put on Source Forge at http://10.120.16.16/sf/docman/do/listDocuments/projects.qa_tasks/docman.root.documents.mpp

Product requirement documents are put on Source Forge at http://10.120.16.16/sf/go/doc1152?nav=1 and http://10.120.16.16/sf/go/doc1153?nav=1 . New member needs to go through these documents to get understood the main product of our company.

3.1.2 Test suite

3.1.2.1 Internal test

Test cases are put on Source Forge at http://10.120.16.16/sf/docman/do/listDocuments/projects.qa_tasks/docman.root.test_plan_test_cases.mpp

The test cases are executed both manually and automatically. With respect to the automated test cases, they are implemented with both Expect (Tcl) script, SoapUI test tool and Quick Test Pro.

Test scripts of EWallet which are implemented to test the product automatically are controlled by the SVN integrated in Source Forge also. They can be committed and updated by setting up the Tortoise SVN at tester’s PC. The url of repository is http://10.120.16.16/svn/repos/qarepo/newJConsole

The performance of product is tested by Load Runner test tool. The relevant scripts are implemented to simulate multi connections to access the system under test or generate a lot of data for system under test.

3.1.2.2 Integration test: TBD

API test End to end test

3.2 Topup website

Topup wessite is an e-commerce website which has been constructed to supply to online customers the service of buying topup cards. Beside the purpose of selling topup cards, this website is to use the payment method which is our Ewallet product. Customers have to create ewallets and load money to ewallets in order to pay for the topup cards that they buy. This sms gateway is integrated with Ewallet via Checkout function of Ewallet.

3.2.1 Documents

All documents relating to Topup website is put on Source Forge at http://10.120.16.16/sf/docman/do/listDocuments/projects.qa_tasks/docman.root.documents.topup

Product requirement document is put on Source Forge at http://10.120.16.16/sf/go/doc1257?nav=1 . New member needs to go through this document to get understood the main product of our company.

3.2.2 Test suite

Test cases are put on Source Forge at http://10.120.16.16/sf/docman/do/listDocuments/projects.qa_tasks/docman.root.test_plan_test_cases.topup The test cases are executed only manually.

3.3 Topup SMS

Topup SMS is a sms gateway which has been constructed to supply to mobile user the service of buying topup cards via sms. Beside the purpose of selling topup cards, this product is to use the payment method which is our Ewallet product. Customers have to create ewallets and load money to ewallets in order to pay for the topup cards that they buy. This sms gateway is integrated with Ewallet via Direct Charge function of Ewallet.

3.3.1 Documents

All documents relating to Topup SMS is put on Source Forge at http://10.120.16.16/sf/docman/do/listDocuments/projects.qa_tasks/docman.root.documents.topupsms

Product requirement document is put on Source Forge at http://10.120.16.16/sf/go/doc1330?nav=1 . New member needs to go through this document to get understood the main product of our company.

3.3.2 Test suite

Test cases are put on Source Forge at http://10.120.16.16/sf/docman/do/listDocuments/projects.qa_tasks/docman.root.test_plan_test_cases.topupsms The test cases are executed manually by using Soap UI test tool to input data into the web service of smsd.

3.4 Taxi payment (Mai Linh taxi)

Mai Linh Taxi Payment is a system that help Mai Linh Group's taxi passengers pay taxi fare easier, quicker and safer with just one SMS. It interfaces with Mobivi's SMS system to receive payment requests from passengers, keep track and coordinate with Mobivi's ewallet system to process the requests. Once the requests are processed, both driver and passenger receive confirmation from the system. This sms gateway is integrated with Ewallet via Direct Charge function of Ewallet.

3.4.1 Documents

All documents relating to Taxi payment product is put on Source Forge at http://10.120.16.16/sf/docman/do/listDocuments/projects.qa_tasks/docman.root.documents.taxi_payment

Product requirement document is put on Source Forge at http://10.120.16.16/sf/go/doc1309?nav=1 . New member needs to go through this document to get understood the main product of our company.

3.4.2 Test suite

Test cases are put on Source Forge at http://10.120.16.16/sf/docman/do/listDocuments/projects.qa_tasks/docman.root.test_plan_test_cases.taxi_payment The test cases are executed manually by using Soap UI test tool to input data into the web service of smsd.

3.5 Remittance

Remittance is a system managing the remittance transfers which are typically cross-border person-to-person payments and of low monetary value.

3.5.1 Documents

All documents relating to Taxi payment product is put on Source Forge at http://10.120.16.16/sf/docman/do/listDocuments/projects.qa_tasks/docman.root.documents.remittance

Product requirement document is put on Source Forge at http://10.120.16.16/sf/go/doc1187?nav=1 . New member needs to go through this document to get understood the main product of our company.

3.5.2 Test suite

Test cases are put on Source Forge at http://10.120.16.16/sf/docman/do/listDocuments/projects.qa_tasks/docman.root.test_plan_test_cases.remittance The test cases are executed only manually.

3.6 Bank tool

Bank tool is an admin tool that suppors managing and operating the transactions and reports of ewallet.

3.6.1 Documents

All documents relating to Bank tool product is put on Source Forge at http://10.120.16.16/sf/docman/do/listDocuments/projects.qa_tasks/docman.root.documents.mpp.bank_tool

3.6.2 Test suite

Test cases are put on Source Forge at http://10.120.16.16/sf/go/doc1346?nav=1

The test cases are executed automatically and manually.

3.7 Agent tool

Agent tool is an admin tool that suppors managing, operating the agents, pricing policies and importing topup-keys for the topup system.

3.7.1 Documents

All documents relating to Agent tool product is put on Source Forge at http://10.120.16.16/sf/docman/do/listDocuments/projects.qa_tasks/docman.root.documents.topup.agent_tool

3.7.2 Test suite

Test cases are put on Source Forge at http://10.120.16.16/sf/docman/do/listDocuments/projects.qa_tasks/docman.root.test_plan_test_cases.topup

The test cases are executed only manually.

3.8 Money Transfer Soap

Money Transfer Soap is a web service to integrate with Dong A Bank. It supports transferring money between bank accounts of Dong A Bank and ewallets.

3.8.1 Documents

All documents relating to Money Transfer Soap product is put on Source Forge at http://10.120.16.16/sf/docman/do/listDocuments/projects.qa_tasks/docman.root.documents.mpp.money_transfer_soap

3.8.2 Test suite

Test cases are put on Source Forge at http://10.120.16.16/sf/go/doc1345?nav=1 . The test cases are executed only automatically.

Test scripts of Money Transfer Soap which are implemented to test the product automatically are controlled by the SVN integrated in Source Forge also. They can be committed and updated by setting up the Tortoise SVN at tester’s PC. The url of repository is http://10.120.16.16/svn/repos/qarepo/newJConsole/moneytransfersoap

3.9 Otpcmd

Otpcmd is a service to integrate with ewallet and supports performing the transactions via sms and mobile app.

3.9.1 Documents

All documents relating to Otpcmd product is put on Source Forge at http://10.120.16.16/sf/docman/do/listDocuments/projects.qa_tasks/docman.root.documents.mpp.otpcmd

3.9.2 Test suite

Test cases are put on Source Forge at http://10.120.16.16/sf/go/doc1369?nav=1 . The test cases are executed automatically and manually.

Test scripts of Money Transfer Soap which are implemented to test the product automatically are controlled by the SVN integrated in Source Forge also. They can be committed and updated by setting up the Tortoise SVN at tester’s PC. The url of repository is http://10.120.16.16/svn/repos/qarepo/newJConsole/ otpcmd

4. Guidelines and Templates

4.1 Guidelines

4.1.1 Using Linux OS

Access the following website to get acquainted to the common commands on Linux and to practice them: http://www.ss64.com/bash/

4.1.2 Necessary software to install

Putty VMWare Infrastructure Client JXplorer Winscp Ultra Edit Tortoise SVN SnagIt 8 UltraVNC SoapUI pro SQLYog

Notes: New member is required to install these above software which are essential for his/her job. Source of all software are put at \\10.120.20.16\softwares

4.1.3 Setup systems

4.1.3.1 Internal test

To prepare a system under testing, there’re 2 necessary things to setup: machines and build.

Guideline to setup a virtual machine is put on Source Forge at http://10.120.16.16/sf/go/doc1207?nav=1

Guidelines to install build and configure the system are described in details and put on Source Forge- Install and configure EWallet: http://10.120.16.16/sf/go/doc1205?nav=1

4.1.3.2 Integration test: TBD

4.1.4 Using Test tools

Expect (Tcl): - The tutorial website of this script can be accessed at

http://www.tcl.tk/man/tcl8.5/tutorial/tcltutorial.html - The instruction (readme file) of installing Expect can be checked out from SVN

of Source Forge at http://10.120.16.16/integration/viewcvs/viewcvs.cgi/newJConsole/Install%20TCL.txt?root=qarepo&rev=2344&system=exsy1002&view=log

Load Runner: Source and tutorial of Load Runner can be got from \\10.120.20.16\softwares .

SoapUI: Source and tutorial of SoapUI can be got from \\10.120.20.2\Software. Bank API Web Test Tool: The test tool which was developed by the developers of

Mobivi supports testing API between Mobivi systems (both Ewallet and MSS) and Core Bank. It can be got by checking out source code from Engineering SVN.

Stock API Test Tool: The test tool which was developed by the developers of Mobivi supports testing API between Mobivi systems (both Ewallet and MSS) and Trading System. It can be got by checking out source code from Engineering SVN.

4.1.5 Setup automation test

- After checking out the test scripts from SVN of Source Forge, the instruction is also enclosed. Following the instruction (usually as readme file) step by step then the test scripts can be run on system under test.

4.2 Templates

4.2.1 Test case

Template of test case helps to design test case correctly and consistently. It is put on Source Forge at http://10.120.16.16/sf/go/doc1047?nav=1

4.2.2 Bug

Template of bug helps to report bug correctly with enough necessary information. It is put on Source Forge at http://10.120.16.16/sf/go/doc1024?nav=1

5. Others

5.1 Inventories of team:

The inventories list includes all equipments belong to QA team: machines, mobiles, sim card, blue tooth USB … It is put on Source Forge at http://10.120.16.16/sf/go/doc1023?nav=1 . Manager will update this list frequently and inform team members which equipment is available.

5.2 Release management

All released builds and patchs and their release notes, issues are tracked for reference and can be viewed at http://10.120.16.16/sf/go/doc1254?nav=1 .

6. Training Schedule

Each new member will be assigned to 1 buddy (1 team member) who will train and give instructions. The buddy will monitor the training schedule below and review the tasks and execises of new member.

# Task Exercise Duration

1 - Go through #1 and #2

- Access Mantis to view existing bugs and get familiar with the process of reporting bug.- Update task on Source Forge 1 day

2- Go through #3, #4 but not in details.- Install all necessary software - Create a VM 2 days

3 - Go through again the #4.1.1 in details- Practise the Linux commands on created VM 1 day

4 - Go through again the #4.1.3.1 in details - Install and configure Ewallet build 1 day

5

- Go through again the PRD in #3.1.1 in details- Go through the #4.2- Test the Ewallet

- Design test cases for 1 function- Report bug if any 2 days

6- Go through #4.1.4 and #4.1.5 - Go through #3.1.2

- Run test scripts of 1 function of MPP and report results 2 day