Slide 1

Slide 1 text

Confidential Japanese slides here Merpay QA DevDojo

Slide 2

Slide 2 text

2 Confidential Speaker Introductions Masatoshi Sato / @satomasa Masatoshi spent roughly a decade working for a third-party verification company, where he acquired experience working on QA of a variety of systems. He then worked on QA at a number of business companies before joining Merpay. At Merpay, he is in charge of QA of merchant-related features on the Partner Platform Team. Yasuhiro Kawasaki / @Yasuhiro Yasuhiro started his career at a cram school straight out of university, and then took an interest in software development and shifted his career toward the tech industry. He has been working in testing ever since. He joined Merpay in October of 2021, where he is in charge of QA for credit-related services.

Slide 3

Slide 3 text

3 Confidential Agenda What is QA? The QA Process 01 02 03 QA is for Everyone 04 Summary

Slide 4

Slide 4 text

Confidential What is QA? 4

Slide 5

Slide 5 text

5 Confidential What is QA? What is QA? QA stands for quality assurance.

Slide 6

Slide 6 text

6 Confidential "Quality is value to some person." —Gerald M. Weinberg What is QA?

Slide 7

Slide 7 text

7 Confidential The level of quality required varies depending on the conditions and situation. The fundamental concept of quality assurance is how we assure and verify that the required level of quality is provided reliably. What is QA?

Slide 8

Slide 8 text

8 Confidential Example of Quality Assurance ● Establishment of Quality Standards ○ Setting standards to meet a certain level of quality ● Standardization of Documents ○ Standardization of formats for specifications, development design documents, test cases, etc ● Development Process Optimization ○ Optimizing the development process to ensure quality 
 What is QA?

Slide 9

Slide 9 text

Confidential Why is QA necessary? 9

Slide 10

Slide 10 text

Confidential Releasing without performing proper QA leads to higher risk of incidents and the following potential risks: ● Reliability decline ● Additional costs ● Legal risks What is QA?


Slide 11

Slide 11 text

11 Confidential ● Reliability decline If incidents occur frequently, trust in our products and services declines, and we risk losing the trust of our customers and the market. ・Loss of customers ・Decrease in customer satisfaction and damage to our  brand image ・Impact on future revenue and growth What is QA?

Slide 12

Slide 12 text

12 Confidential ● Additional costs We may incur additional costs (time, money, etc.) for incident handling and recovery tasks. What is QA?

Slide 13

Slide 13 text

13 Confidential What is QA? ● Legal risks If incidents that infringe on legal requirements occur, it may cause a major social problem. (We may be forced to suspend our business.)

Slide 14

Slide 14 text

14 Confidential QA is highly crucial in order to avoid these risks. What is QA?

Slide 15

Slide 15 text

15 Confidential Next, we will introduce the QA process at Merpay. What is QA?

Slide 16

Slide 16 text

Confidential Merpay QA Process 16

Slide 17

Slide 17 text

17 Confidential QA Process Overview 1. Consider specs 2. Development design and implementation 3. Testing 4. Operations Test planning Spec review Test design Test execution Production QA Regression testing QA engineers are involved in every phase, from deciding the specs to the actual operations.

Slide 18

Slide 18 text

18 Confidential Phase 1: Consider specs ● Attend spec review sessions ○ Check impact on existing system/other microservices ○ Make suggestions based on past experience ● Analyze and plan tests ○ Determine scope of tests ○ Decide on plan for testing ○ Determine risks ○ Scheduling

Slide 19

Slide 19 text

19 Confidential Phase 2: Development design and implementation ● Design tests ○ Create test viewpoints and test cases ○ Hold test case review sessions ○ Implement test code ● Attend development design review sessions ● Perform readiness check

Slide 20

Slide 20 text

20 Confidential Phase 3: Testing ● Execute tests ○ API and UI tests ○ Regression tests (including automation) ● Analyze bugs ○ Visualize bugs and analyze bug trends ● Perform dogfooding ○ Test features on employees before release

Slide 21

Slide 21 text

21 Confidential Phase 4: Operations ● Production check ○ Test features after release to check for issues ● Regression testing ○ Do regression testing regularly ○ Perform regression maintenance ● Improve automated testing ○ Perform maintenance on automated tests ● Improve upon issues ○ Hold retrospectives, etc.

Slide 22

Slide 22 text

22 Confidential The QA Process The basic process is similar for all teams, but in some cases operations may differ slightly, so please check with the QA engineer of the relevant team for details. Also! At Merpay, QA engineers are involved in every step along the way, from deciding the specs to the release and the operations after release, so please don’t hesitate to get us involved in any small way!

Slide 23

Slide 23 text

Confidential QA is for Everyone
 23

Slide 24

Slide 24 text

24 Confidential Is QA something only the QA Team and QA engineers should remain aware of? QA is for Everyone

Slide 25

Slide 25 text

25 Confidential Is QA something only the QA Team and QA engineers should remain aware of? QA is for Everyone No, not at all! It’s important that not only the QA Team but everyone maintain a common awareness toward quality assurance.

Slide 26

Slide 26 text

26 Confidential People of all roles, in every process, should aim to deliver the very best quality, and continue to make improvements. This creates a product of higher value. QA is for Everyone

Slide 27

Slide 27 text

27 Confidential ○ Implementing and furthering automated tests ■ Work with backend and frontend engineers to further automated testing ● Installation and Operation of scenarigo ○ Improving QA efficiency ■ Work together to consider ways to ensure quality effectively, and make QA tasks more efficient ● GoによるSQLクエリテストの取り組み ○ Holding retrospectives for incidents ■ When an incident occurs, the whole team should consider ways that the team (not an individual) can prevent reoccurrences, and implement improvement measures QA is for Everyone

Slide 28

Slide 28 text

28 Confidential QA(Quality Assurance) is assuring and verifying quality Inadequate QA(Quality Assurance) can lead to the occurrence of risks QA(Quality Assurance) is for everyone—let’s work together to create the very best product 02 03 01 Summary

Slide 29

Slide 29 text

Confidential Thank you for listening! 29