APPROACH TO IMPROVEMENT OF TEST PROCESS USING TOOLS

Transcript

1. APPROACH TO IMPROVEMENT OF TEST PROCESS USING TOOLS Rijun Suzuki LINE Corporation
2. • 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
4. • Introduce LINE / QA Organization • Problems to Solve • Selection Point of Tools • Introduction Effect • Current situation / Outlook Agenda
5. • Introduce LINE / QA Organization • Problems to Solve • Selection Point of Tools • Introduction Effect • Current situation / Outlook Agenda
6. PRODUCT
7. ABOUT LINE SERVICE Realization of smart portal LINE's growth strategy Advertisement Core business Strategic business Commerce messenger platform
8. ABOUT LINE USERS million Indonesia Thailand Taiwan Japan monthly active users (MAU)
9. QA ORGANIZATION
10. INTRODUCE LINE QA ORGANIZATION Over 100 Engineers QA & Automation 5 Countries
11. INTRODUCE LINE QA ORGANIZATION
12. • Introduce LINE / QA Organization • Problems to Solve • Selection Point of Tools • Introduction Effect • Current situation / Outlook Agenda
13. • 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?
14. • 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?
15. TEST MANAGEMENT CATEGORY ref. State of Testing Report 2018 Which category should focus on?
16. TEST MANAGEMENT CATEGORY ref. State of Testing Report 2018 Which category should focus on?
17. • Want to achieveɿTo increase the efficiency of the test • In particularɿ • Make discipline • Improved visibility (transparency) WHAT IS OUR GOAL?
18. • 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
19. • Introduce LINE / QA Organization • Problems to Solve • Selection Point of Tools • Introduction Effect • Current situation / Outlook Agenda
20. SELECTION POINT OF TOOLS ref. State of Testing Report 2018
21. SELECTION POINT OF TOOLS ref. State of Testing Report 2018 We thought about what to use to manage the test
22. TYPE COMPARISON Cooperation with BTS Cost Interface BTS plugin like ˕ ˚ ✖ Spreadsheet like(Excel) ✖ ̋ ̋ Dedicated tool ̋ ˚ ̋ Checkpoint example Compare tool types and compare tools themselves
23. TYPE COMPARISON Cooperation with BTS Cost Interface BTS plugin like ˕ ˚ ✖ Spreadsheet like(Excel) ✖ ̋ ̋ Dedicated tool ̋ ˚ ̋ Checkpoint example Compare tool types and compare tools themselves
24. • Introduce LINE / QA Organization • Problems to Solve • Selection Point of Tools • Introduction Effect • Current situation / Outlook Agenda
25. • Want to achieveɿTo increase the efficiency of the test • In particularɿ • Make discipline • Improved visibility (transparency) INTRODUCTION EFFECT achieved these?
26. 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
27. 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
28. • Introduce LINE / QA Organization • Problems to Solve • Selection Point of Tools • Introduction Effect • Current situation / Outlook Agenda
29. • 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
30. THANK YOU