SETA InternationalQuality Management Introduction

Nguyen Thanh HuyenApril 2014

1

Contents1. Company introduction2. Self introduction3. Ways used for quality management4. Types of software testing5. Automated testing6. Software Development Processes7. Training functional testing for DEV8. QA Training9. Training creating test matrix10. Mushi tool11. Discussion

1. Company introduction2. Self introduction3. Ways used for quality management4. Types of software testing5. Automated testing6. Software Development Processes7. Training functional testing for DEV8. QA Training9. Training creating test matrix10. Mushi tool11. Discussion

2

Company introduction• Seta International

Vietnam wasestablished in 2013

• Now we have 153staffs including:– BSE: 16 members– DEV: 108members– QA: 26 members– Comtor: 3 members

• Seta InternationalVietnam wasestablished in 2013

• Now we have 153staffs including:– BSE: 16 members– DEV: 108members– QA: 26 members– Comtor: 3 members

JapanVietnam

America3

Self introduction• My name is Nguyen Thanh

Huyen, QA Manager• I come from Hanoi• I have 9 years of QA

experience for Japanesecompanies

• My hobbies are traveling andcooking

• My name is Nguyen ThanhHuyen, QA Manager

• I come from Hanoi• I have 9 years of QA

experience for Japanesecompanies

• My hobbies are traveling andcooking

• I love my job because it’s very challenging and it's also great whenQA involved projects get high quality and praises from customers

• My team has 29 members. All of them are skilled and professional

4

Ways used for quality management1. For the Project Explaining SRS(*1) and checking specification

comprehension of developers (by review functionaltesting for DEV)

Analyzing & confirming & controlling CR(*2) Applying appropriate types of software testing for each

project Applying automated testing to minimize workload Applying flexible process for each project

2. For Member DEV: ProjectsTraining functional testing for developers QA: Training QA members methodically: tester -->

SQA(*3) --> QAE(*4)--> PQA(*5) --> QAL(*5)

1. For the Project Explaining SRS(*1) and checking specification

comprehension of developers (by review functionaltesting for DEV)

Analyzing & confirming & controlling CR(*2) Applying appropriate types of software testing for each

project Applying automated testing to minimize workload Applying flexible process for each project

2. For Member DEV: ProjectsTraining functional testing for developers QA: Training QA members methodically: tester -->

SQA(*3) --> QAE(*4)--> PQA(*5) --> QAL(*5)

5

Types of software testing• Smoke testing• GUI testing• Functional testing• Exploratory testing• API testing• Scenario testing• Bug fixed testing• Regression testing• Acceptance testing

• Performance testing• Load testing• Stress testing• Security testing• Regression testing

• Smoke testing• GUI testing• Functional testing• Exploratory testing• API testing• Scenario testing• Bug fixed testing• Regression testing• Acceptance testing

• Performance testing• Load testing• Stress testing• Security testing• Regression testing

6

Manual test

Auto test

Automated testing (1/2)

• Web PC’s auto test tool– Selenium– Jmeter

• AOS app’s auto test tool– Robotium

• iOS app’s auto test tool– UI Automation

• iOS & AOS app’s autotest tool– Calabash

• Test Cloud Service

• Web PC’s auto test tool– Selenium– Jmeter

• AOS app’s auto test tool– Robotium

• iOS app’s auto test tool– UI Automation

• iOS & AOS app’s autotest tool– Calabash

• Test Cloud Service

7

Automated testing (2/2)

• When to apply:– Regression testing

should be performed– Testing on many devices

or platforms– Objects of automated

testing must be stableapplications

• Why:– Improve test efficiency– Improve the regression

test– Minimize workload– Resource utilization– Easily reproduce bugs

• When to apply:– Regression testing

should be performed– Testing on many devices

or platforms– Objects of automated

testing must be stableapplications

• Why:– Improve test efficiency– Improve the regression

test– Minimize workload– Resource utilization– Easily reproduce bugs

8

Testing time decreases 60.4% when auto testing isapplied for regression test. (5 devices, 20 scenario testcases, 20 time regression test)

Software Development Processes

SPRINT 1Make test

casesテストケースの作成

Fixed bug & re-test不具合修正・確認

Coding開発

Test & fixbugs & re-

test

ReviewTest casesレビュー

MakeTest cases作成

Test & Re-test試験・回帰

ReviewTest casesレビュー

Review sourceソースコードレビュー

Test & Re-test試験・回帰

CustomerConfirm

Flexible: Comfirmevery sprint

BSE DEV QA

ALL Customer

9

Proposal提案

Preparation準備

ReviewTest casesレビュー

Review sourceソースコードレビュー

Test & Re-test試験・回帰

SPRINT 2SPRINT 2

。。。。。。。。。。

SPRINT nSPRINT n

Closing終了

Flexible: Comfirmevery sprint

Common:Confirm atend of Sprints

CustomerConfirm

OKNG

Communication in Project

BSEHanoi

BSETokyo

Japanese

Japanese

10

Customer

DEV

DEV DEV

QA QA

QA

Japanese

Vietnamese

Training functional testing for developers

• Why:– Making sure programs

are installed correctlyaccording tospecifications

– Making sure programsrun correctly in validcases

– Making sure NOfunctional bug releasedto QA

• How:

SpecCreate

FTCoding FT AT

Cus

tom

er

Dev

elop

er

QA

/BSE

• Why:– Making sure programs

are installed correctlyaccording tospecifications

– Making sure programsrun correctly in validcases

– Making sure NOfunctional bug releasedto QA

Cus

tom

er

Dev

elop

er

QA

/BSE

11

Number of bugs decreases 60%when functional testing is appliedfor development team.

QA Training• Training creating test matrix• Training reporting & analyzing & confirming bugs• Training reviewing functional testing of developers• Training auto test tools• Training project management• Training Software Development Processes• Building common test view points (400 points) and test

experiencesMaking test-cases auto-generating tool(Mushi tool)

• Training Japanese

• Training creating test matrix• Training reporting & analyzing & confirming bugs• Training reviewing functional testing of developers• Training auto test tools• Training project management• Training Software Development Processes• Building common test view points (400 points) and test

experiencesMaking test-cases auto-generating tool(Mushi tool)

• Training Japanese

12

Training creating test matrix

EntranceCeremony• Explain meeting• Excite

EntranceCeremony• Explain meeting• Excite

Test designpreparation• Specification

preparationreviews

• Specificationreviews

Test designpreparation• Specification

preparationreviews

• Specificationreviews

Test design（matrix）• Add QA-ID• Create matrix• Review matrix• Update matrix

Test design（matrix）• Add QA-ID• Create matrix• Review matrix• Update matrix

Test cases• Create test cases• Review test cases• Update test

cases

Test cases• Create test cases• Review test cases• Update test

cases

Graduationexercises

Graduationexercises

13

EntranceCeremony• Explain meeting• Excite

EntranceCeremony• Explain meeting• Excite

Test designpreparation• Specification

preparationreviews

• Specificationreviews

Test designpreparation• Specification

preparationreviews

• Specificationreviews

Test design（matrix）• Add QA-ID• Create matrix• Review matrix• Update matrix

Test design（matrix）• Add QA-ID• Create matrix• Review matrix• Update matrix

Test cases• Create test cases• Review test cases• Update test

cases

Test cases• Create test cases• Review test cases• Update test

cases

Graduationexercises

Graduationexercises

1 week 1 week1 ~ 2 weeks

Mushi tool

14

Creating time decreases 40% when Mushitool is applied for creating test cases

Discussion

15

Appendix

• SRS(*1): Software requirements specification• CR(*2) : Change request• SQA(*3) : Software Quality Assurance• QAE(*4): QA engineer (auto test tool)• PQA(*5): Process Quality Assurance• QAL(*5): QA Leader

• SRS(*1): Software requirements specification• CR(*2) : Change request• SQA(*3) : Software Quality Assurance• QAE(*4): QA engineer (auto test tool)• PQA(*5): Process Quality Assurance• QAL(*5): QA Leader

16

Thank you for your listening!!!

17