Share
Embed
The result of E2E Automated Testing to Improve Productivity & Quality
Hiroyuki Okuda (LINE Fukuoka / QA Engineering 1 Team / QA Engineer)
https://tech-verse.me/ja/sessions/97
https://tech-verse.me/en/sessions/97
https://tech-verse.me/ko/sessions/97
Tech-Verse2022
November 18, 2022
Transcript
79 slides
-
- 2020:LINE Fukuoka QA Engineer LINE Front-end Framework (LIFF) →
LINE DEVELOPER DAY2021 - 2021:Authentication and Authorization Platform - 2022 :ID Federation(LINE,Yahoo! JAPAN,PayPay) -
E2E(End to End) Test Automation - Early Stages - Automate
Most of E2E Testing Topic Learned from Experience -
E2E Test Automation - Early Stages - Automate Most of
E2E Testing Topic Learned from Experience -
Authentication and Authorization Platform PM Developer QA 2 15 2
Project Structure -
Week 1 ・・・ Week N Test Phase Developer QA ʢAS
ISʣ Development Process Scenario Test Design Implementation Test Design Implementation Test Design Implementation Test Bug Fix -
Week 1 ・・・ Week N Test Phase Developer QA ʢAS
ISʣ Development Process Over 30 Screens Scenario Test Plan Scenario Test Design Implementation Test Design Implementation Test Design Implementation Test Bug Fix -
%JWJEF#JH5BTLT Problem Scenario Test Plan Scenario Test 3 Risk of
Bugs 2 Not Understanding the Specifications 1 High Planning Volume -
Week 1 ・・・ Week N Test Phase Developer QA ʢAS
ISʣ QA (TO BE) %JWJEF#JH5BTLT Scenario Test Plan Scenario Test E2E Testing of Each Screen Scenario Test Scenario Test Plan Bug Fix Design Implementation Test Design Implementation Test Design Implementation Test -
Week 1 ・・・ Week N Test Phase Developer QA ʢAS
ISʣ QA (TO BE) %JWJEF#JH5BTLT Purpose1 Bug Fix Design Implementation Test Design Implementation Test Design Implementation Test Scenario Test Plan Scenario Test E2E Testing of Each Screen Scenario Test Scenario Test Plan 1 High Planning Volume Reduce the Test Plan Testing Ahead of Schedule -
Week 1 ・・・ Week N Test Phase Developer QA ʢAS
ISʣ QA (TO BE) %JWJEF#JH5BTLT Purpose2 Bug Fix Design Implementation Test Design Implementation Test Design Implementation Test Scenario Test Plan Scenario Test E2E Testing of Each Screen Scenario Test Scenario Test Plan 2 Not Understanding the Specifications Reduce the Difficulty of Planning Understanding through Testing -
Week 1 ・・・ Week N Test Phase Developer QA ʢAS
ISʣ QA (TO BE) %JWJEF#JH5BTLT Purpose3 Bug Fix Design Implementation Test Design Implementation Test Design Implementation Test Scenario Test Plan Scenario Test E2E Testing of Each Screen Scenario Test Scenario Test Plan Reduce Initial Bugs 3 Risk of Bugs Detect Bugs in Advance -
Test Automation Background1 Week 1 ・・・ Week N Test Phase
Developer QA (TO BE) Regression Testing Required Constantly Updated Bug Fix Design Implementation Test Design Implementation Test Design Implementation Test E2E Testing of Each Screen Scenario Test Scenario Test Plan -
Authentication and Authorization Platform PM Developer QA 2 15 2
Test Automation ・Internal System ・Long Term Maintenance by Small Team Background2 -
Test Automation Background Before Launch Regression Testing Required After Launch
Small Team, Wide Coverage Test Automation -
E2E Automation Target Functional Test Script Test Non-Script Test Exploratory
Test Ad Hoc Test General Manual Manual or Auto Select Regression Test -
E2E Automation Target Functional Test Script Test Non-Script Test Exploratory
Test Ad Hoc Test My Project Regression Test All Basic Policy is Auto Basic Policy is Auto -
Quality Week 1 ・・・ Week N Test Phase Developer QA
(TO BE) Bug Fix Design Implementation Test Design Implementation Test Design Implementation Test E2E Testing of Each Screen Scenario Test Scenario Test Plan Regression Test 1 Keep Quality 2 Find Bugs Quickly -
Manual Test Productivity Test Run Evidence by Manual Process Test
Design Test Implementation Text Automation Test Design Document Design Document -
Manual Test Productivity Test Run Evidence by Manual Process Test
Design Test Implementation Text Automation Test Test Run Test Design Test Implementation MagicPod Evidence by MagicPod Design Document Design Document -
Productivity Week 1 ・・・ Week N Test Phase Developer QA
(TO BE) Bug Fix Design Implementation Test Design Implementation Test Design Implementation Test E2E Testing of Each Screen Scenario Test Scenario Test Plan Regression Test Constantly Updated Maintenance Required -
Productivity Maintainability Shared Variables Shared Steps Shared UI Capture Data
Pattern Improved Maintainability -
Result Week 1 ・・・ Week N Test Phase Developer QA
(TO BE) Bug Fix Design Implementation Test Design Implementation Test Design Implementation Test E2E Testing of Each Screen Scenario Test Scenario Test Plan 37Screens 600Cases -
Quality Productivity Result 1 Keep Quality Run Daily. Total Time
is 1 hour 37Screens 600Cases 2 Find Bugs Quickly Find on the Day the Bugs Occurs Created and Maintained by 2Members -
Manual Test Testing Quality and Productivity Test Run Evidence by
Manual Process Test Design Test Implementation Text Automation Test Test Run Test Design Test Implementation MagicPod Evidence by MagicPod Design Document Design Document Nature Language Computer Language -
Text (Nature Language) MagicPod (Computer Language) Testing Quality and Productivity
Click https://〇〇/ Navigate to URL LoginID Area △△ Input Login Button Password Area □□ Input to to -
Login Input Password Input login ID Moves to login screen
Click Login Button Text (Nature Language) MagicPod (Computer Language) Testing Quality and Productivity Click Abstract Concrete https://〇〇/ Navigate to URL LoginID Area △△ Input Login Button Password Area □□ Input to to Login ID? Password? Need Rules Lack of Information -
Login Input Password Input login ID Moves to login screen
Click Login Button Text (Nature Language) MagicPod (Computer Language) Testing Quality and Productivity Click Abstract Concrete https://〇〇/ Navigate to URL LoginID Area △△ Input Login Button Password Area □□ Input to to Concrete Login ID? Password? Need Rules Lack of Information -
Manual Test Testing Quality and Productivity Test Run Evidence by
Manual Process Test Design Test Implementation Text Automation Test Test Run Test Design Test Implementation MagicPod Evidence by MagicPod Design Document Design Document Nature Language Computer Language -
Manual Test Testing Quality and Productivity Test Run Evidence by
Manual Process Test Design Test Implementation Text Automation Test Test Run Test Design Test Implementation MagicPod Evidence by MagicPod Design Document Design Document Nature Language Computer Language Computer Language × MagicPod -
E2E Test Automation - Early Stages - Automate Most of
E2E Testing Topic Learned from Experience -
Beginning Middle Part Preparation Key Factor of Automation Automation Plan
Before Increasing Test Cases To Improve Product Quality -
Beginning Middle Part Preparation Key Factor of Automation Automation Plan
Before Increasing Test Cases To Improve Product Quality Plan ⇄ Learn -
Manual Test Before Increasing Test Cases Test Run Evidence by
Manual Process Test Design Test Implementation Text Automation Test Test Run Evidence by MagicPod Test Design Test Implementation MagicPod -
Manual Test Before Increasing Test Cases Test Run Evidence by
Manual Process Test Design Test Implementation Text Mix Test Design Automation Test Test Run Evidence by MagicPod Test Design Test Implementation MagicPod Test Run Evidence by Manual Test Implementation Text Test Run Evidence by MagicPod Test Implementation MagicPod × -
Manual Test Before Increasing Test Cases Test Run Evidence by
Manual Process Test Design Test Implementation Text Mix Test Design Automation Test Test Run Evidence by MagicPod Test Design Test Implementation MagicPod Test Run Evidence by Manual Test Implementation Text Test Run Evidence by MagicPod Test Implementation MagicPod × Difficult to Reduce -
Before Increasing Test Cases Test Case Simply Increase Regular and
Parallel Execution Test Case1 Test Case2 Test Case3 Manual Test Case1 Test Case2 Test Case3 Parallel Serial Regular CI Tool -
Before Increasing Test Cases Test Case Simply Increase Regular and
Parallel Execution Test Case1 Test Case2 Test Case3 Manual Test Case1 Test Case2 Test Case3 Parallel Serial Regular Many Update CI Tool -
Beginning Middle Part Preparation Key Factor of Automation Automation Plan
Before Increasing Test Cases To Improve Product Quality Plan ⇄ Learn Create the Final Form Quickly -
E2E Automation Target Functional Test Script Test Non-Script Test Exploratory
Test Ad Hoc Test General Regression Test All Basic Policy is Auto Basic Policy is Auto -
To Improve Product Quality Automation Test Test Run Evidence by
MagicPod Test Design Test Implementation MagicPod Find Any Strange Activity Test Run Ad Hoc Test -
Beginning Middle Part Preparation Key Factor of Automation Automation Plan
Before Increasing Test Cases To Improve Product Quality Plan ⇄ Learn Create the Final Form Quickly Mix Non-Script Test -
What Non-coding Tool Give Us Example from Another Project AS
IS TO BE Manual Tester Selemium,Appium Automation Engineer Integration Manual E2E Automated E2E -
What Non-coding Tool Give Us Example from Another Project AS
IS TO BE Manual Tester Selemium,Appium Automation Engineer MagicPod Integration Manual E2E Automated E2E Manual Tester Manual Tester -
What Non-coding Tool Give Us Example from Another Project Shared
Variables Shared Steps Shared UI Capture Data Pattern MagicPod Features Not Used Low Maintainability -
What Non-coding Tool Give Us Example from Another Project Manual
Tester Selemium,Appium Automation Engineer MagicPod Manual Tester Runnable Test Case Good Test Case Skill Test Programing AS IS TO BE Integration Manual E2E Automated E2E Manual Tester -
What Non-coding Tool Give Us Example from Another Project Manual
Tester Selemium,Appium Automation Engineer MagicPod Manual Tester Runnable Test Case Good Test Case Skill Test Programing AS IS TO BE Integration Manual E2E Automated E2E Manual Tester E2E Automation Growth Opportunity -
What Non-coding Tool Give Us Example from Another Project Manual
Tester Selemium,Appium Few Members Integration Manual E2E Automated E2E Skill Test Non-coding Tool Programing Everyone Far -
Conclusion E2E test automation contributes to improved Quality and Productivity.
The use of non-coding tools allows the team to grow while achieving the results of E2E automation.