QA Experience

Worked on project Betia English, HodooABC, HodooM

Role

QA Engineer

Industry

EdTech

Duration

1.5 years

a cell phone on a table
a cell phone on a table
a cell phone on a table


Overview

I worked in Hodoolabs as a QA engineer, where I spent one and a half years ensuring the quality and usability of digital products.
I worked on ‘Betia English 1,2’, ‘Hodoo ABC’, ‘Hodoo M’ QA project.

This experience strengthened my attention to detail, analytical thinking, and deepened my understanding of user needs.


QA Process

  1. Conduct test based on test case document

Before functional testing, I review the Product Requirements Document (PRD) to understand the intended features. Then, I write test cases that outline the steps needed to trigger each feature and document the entry depth of each UI element.

I conduct testing according to the user flow, ensuring that all functions work smoothly and naturally, and that the interface feels consistent.
If any issues arise, I collaborate with project managers, developers, and designers to make the necessary revisions.


Overview

I worked in Hodoolabs as a QA engineer, where I spent one and a half years ensuring the quality and usability of digital products.
I worked on ‘Betia English 1,2’, ‘Hodoo ABC’, ‘Hodoo M’ QA project.

This experience strengthened my attention to detail, analytical thinking, and deepened my understanding of user needs.


QA Process

  1. Conduct test based on test case document

Before functional testing, I review the Product Requirements Document (PRD) to understand the intended features. Then, I write test cases that outline the steps needed to trigger each feature and document the entry depth of each UI element.

I conduct testing according to the user flow, ensuring that all functions work smoothly and naturally, and that the interface feels consistent.
If any issues arise, I collaborate with project managers, developers, and designers to make the necessary revisions.

a cell phone on a white block
a cell phone on a white block
a cell phone on a white block
two cell phones on a gray surface
two cell phones on a gray surface
two cell phones on a gray surface
  1. Bug report & Monitoring

Once QA testing is complete, I create detailed bug reports and ensure they are assigned to the right person for resolution

Process of fixing bugs

  1. Conducting QA

  2. Make a issue in Jira

  3. Assign a person in charge

  4. Tracking the issue

  5. Reconfirm that the issue is fixed


a cell phone leaning on a ledge
a cell phone leaning on a ledge
a cell phone leaning on a ledge
a pair of cell phones on a concrete block
a pair of cell phones on a concrete block
a pair of cell phones on a concrete block
a cell phone with a yellow rectangular screen
a cell phone with a yellow rectangular screen
a cell phone with a yellow rectangular screen

Reflections

Focusing on user context - Hodoo ABC

After launching Hodoo ABC, an English learning app for children aged 6 to 10, we received multiple user inquiries reporting that children were having difficulty using the service. At this age, children often struggle with concentration, are unfamiliar with touchscreen gestures, and have smaller fingers that make precise tapping difficult. These real-world usage challenges were not fully captured during pre-launch testing.

To better understand user pain points, we reviewed actual gameplay videos submitted by parents. Based on our findings, we made the following key improvements:

1. Added clear tutorials for all game types
2. Introduced motion-based interactions with the game character
3. Enlarged UI elements and expanded touch target areas

Although we had conducted several rounds of internal testing, we failed to fully account for the real usage context of our target users. This experience taught me the importance of testing with actual users in realistic environments, not just relying on desk research or user interviews. By closely observing user behavior and iterating based on real feedback, we were able to significantly improve the user experience and accessibility of the service.

Reflections

Focusing on user context - Hodoo ABC

After launching Hodoo ABC, an English learning app for children aged 6 to 10, we received multiple user inquiries reporting that children were having difficulty using the service. At this age, children often struggle with concentration, are unfamiliar with touchscreen gestures, and have smaller fingers that make precise tapping difficult. These real-world usage challenges were not fully captured during pre-launch testing.

To better understand user pain points, we reviewed actual gameplay videos submitted by parents. Based on our findings, we made the following key improvements:

1. Added clear tutorials for all game types
2. Introduced motion-based interactions with the game character
3. Enlarged UI elements and expanded touch target areas

Although we had conducted several rounds of internal testing, we failed to fully account for the real usage context of our target users. This experience taught me the importance of testing with actual users in realistic environments, not just relying on desk research or user interviews. By closely observing user behavior and iterating based on real feedback, we were able to significantly improve the user experience and accessibility of the service.

Other projects

© 2025. Kyungju Kim All Rights Reserved.

© 2025. Kyungju Kim All Rights Reserved.

© 2025. Kyungju Kim All Rights Reserved.