Building a Quality Management Process as a Solo QA

As a QA engineer joining an environment with no dedicated quality personnel, the focus was on designing a system centered on 'why is this process needed', going beyond simply testing features.

First, the Happy Path, the core flow of the service, was defined, and verification priorities were set based on user proportion and failure risk to efficiently allocate limited resources.

Also, to improve an environment where development and testing were mixed together, a dedicated QA environment was built to increase test reliability, and issue ticket priorities were defined based on issue impact and reproduction frequency, allowing the whole team to communicate using the same criteria.

Finally, the start and end conditions for testing were clearly defined.

• Test start conditions: Completion of self-testing by development/PO/design owners and completion of deployment to the test environment
• Test end conditions: 100% execution of test cases, completion of exploratory testing, and completion of backward compatibility and rollback testing

Through this process, stable quality assurance that accounts for even exceptional situations became possible.