Slide 1

Slide 1 text

APPROACH TO IMPROVEMENT OF TEST PROCESS USING TOOLS Rijun Suzuki LINE Corporation

Slide 2

Slide 2 text

● Rijun Suzuki ● Belongs ● LINE Corporation (2012~) ● Service QA team 1 - Manager ● Other activities ● JaSST Tokyo Executive Committee ● State of Testing Survey 2018 Japanese Translation Project SELF INTRODUCTION

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

• Introduce LINE / QA Organization • Problems to Solve • Selection Point of Tools • Introduction Effect • Current situation / Outlook Agenda

Slide 5

Slide 5 text

• Introduce LINE / QA Organization • Problems to Solve • Selection Point of Tools • Introduction Effect • Current situation / Outlook Agenda

Slide 6

Slide 6 text

PRODUCT

Slide 7

Slide 7 text

ABOUT LINE SERVICE Realization of smart portal LINE's growth strategy Advertisement Core business Strategic business Commerce messenger platform

Slide 8

Slide 8 text

ABOUT LINE USERS million Indonesia Thailand Taiwan Japan monthly active users (MAU)

Slide 9

Slide 9 text

QA ORGANIZATION

Slide 10

Slide 10 text

INTRODUCE LINE QA ORGANIZATION Over 100 Engineers QA & Automation 5 Countries

Slide 11

Slide 11 text

INTRODUCE LINE QA ORGANIZATION

Slide 12

Slide 12 text

• Introduce LINE / QA Organization • Problems to Solve • Selection Point of Tools • Introduction Effect • Current situation / Outlook Agenda

Slide 13

Slide 13 text

● Organize considering various issues ● Organizations are very diverse ● Organizations background also ● Many bases(5 countries~), Consolidation, Outsourcing, Historical background, etc… ● There is no clear rule of the test process ● Adopt various tools, processes by organization ● Do not reuse test documents ● every time making it again ● Each project has different configuration management ● Can not take over ● About growth ● There is no mutual learning ● etc… WHAT IS THE PROBLEM?

Slide 14

Slide 14 text

● Organize considering various issues ● Organizations are very diverse ● Organizations background also ● Many bases(5 countries~), Consolidation, Historical background, etc… ● There is no clear rule of the test process ● Adopt various tools, processes by organization ● Do not reuse test documents ● every time making it again ● Each project has different configuration management ● Can not take over ● About growth ● There is no mutual learning ● etc… Inefficient testing process WHAT IS THE PROBLEM?

Slide 15

Slide 15 text

TEST MANAGEMENT CATEGORY ref. State of Testing Report 2018 Which category should focus on?

Slide 16

Slide 16 text

TEST MANAGEMENT CATEGORY ref. State of Testing Report 2018 Which category should focus on?

Slide 17

Slide 17 text

● Want to achieveɿTo increase the efficiency of the test ● In particularɿ ● Make discipline ● Improved visibility (transparency) WHAT IS OUR GOAL?

Slide 18

Slide 18 text

● Want to achieveɿTo increase the efficiency of the test ● In particularɿ ● Make discipline ● Improved visibility (transparency) WHAT IS OUR GOAL? Solve with test management tools

Slide 19

Slide 19 text

• Introduce LINE / QA Organization • Problems to Solve • Selection Point of Tools • Introduction Effect • Current situation / Outlook Agenda

Slide 20

Slide 20 text

SELECTION POINT OF TOOLS ref. State of Testing Report 2018

Slide 21

Slide 21 text

SELECTION POINT OF TOOLS ref. State of Testing Report 2018 We thought about what to use to manage the test

Slide 22

Slide 22 text

TYPE COMPARISON Cooperation with BTS Cost Interface BTS plugin like ˕ ˚ ✖ Spreadsheet like(Excel) ✖ ̋ ̋ Dedicated tool ̋ ˚ ̋ Checkpoint example Compare tool types and compare tools themselves

Slide 23

Slide 23 text

TYPE COMPARISON Cooperation with BTS Cost Interface BTS plugin like ˕ ˚ ✖ Spreadsheet like(Excel) ✖ ̋ ̋ Dedicated tool ̋ ˚ ̋ Checkpoint example Compare tool types and compare tools themselves

Slide 24

Slide 24 text

• Introduce LINE / QA Organization • Problems to Solve • Selection Point of Tools • Introduction Effect • Current situation / Outlook Agenda

Slide 25

Slide 25 text

● Want to achieveɿTo increase the efficiency of the test ● In particularɿ ● Make discipline ● Improved visibility (transparency) INTRODUCTION EFFECT achieved these?

Slide 26

Slide 26 text

1. DISCIPLINE ✔ Cross-project availability of test cases and information ✔ Configuration of the tool itself makes test cases more reusable ✔ Unify and clarify the work of the person in charge ✔ Test documents are easier to manage assets as a company organization Can reuse Test Run from Test case easily Determine the configuration of the test case

Slide 27

Slide 27 text

2. VISIBILITY ✔ Clarified the relationship between test cases, test results, and BTS tickets by cooperation of BTS ✔ Made the test process more visibility so stakeholders can access test cases and results from BTS / tool easily ✔ There is credibility in progress online on time Test Result of Requirement / Bug Test Case for Requirement

Slide 28

Slide 28 text

• Introduce LINE / QA Organization • Problems to Solve • Selection Point of Tools • Introduction Effect • Current situation / Outlook Agenda

Slide 29

Slide 29 text

● overall the effect was large(I think) ● But, After all, can not be unified at all organization ● There are still a few mainstreams ● Use cases differ depending on the development model ● Probably impossible to standardize everything ● At our organization scale, will conduct “test management” rather than “test control” CURRENT SITUATION / OUTLOOK

Slide 30

Slide 30 text

THANK YOU