How Engineering Impacts QA

At first, I worked in the QC team of a security solution company, checking functional requirements before deployment in line with a Waterfall-based development process. However, repetitive tasks like compatibility testing took up a lot of time, and my focus would scatter, causing me to miss things.

I had a thirst for automation but didn't know where to start, and I was also afraid to apply it in practice. So I moved to a company where automation was already established, and learned the principles of automation by directly running existing code and following scenarios. When code I had manually modified worked correctly, I felt a great sense of fun, and for the first time felt like I had crossed the threshold into Engineering.

At 29CM, I took on Android automation in earnest, writing functional scenarios suited to BVT, and building End-to-End tests that directly called APIs to verify whether data exposure was correct. By finding the necessary APIs in documentation or asking developers to deepen my understanding, I came to understand not just automation but the service itself more deeply.

As I did automation work and started building collaboration tools myself for things like notifications, writing test results, and sharing, my perspective also changed. I gained the confidence that I could actually build features I had previously only imagined, and I began asking questions like "this is inconvenient, isn't there a way to solve it?" more often.

In project QA, using API automation to easily generate test data greatly reduced the resources previously spent on manual work. Because I could create a large amount of data in a short period, I was able to check a wider variety of cases, which resulted in expanding test coverage and shortening the QA period.

Going forward, this kind of work doesn't have to stay as a personal tool — it can be expanded by turning it into a guide that others who need it can use together, reducing the development and testing resources of the entire organization. Ultimately, QA equipped with Engineering can become the center of collaboration that creates more stable, higher-quality services.