Zeny | QA Testing & Exploratory Bug Reporting
Worked on the Zeny project as a QA tester focused on exploratory testing and real user behavior analysis.
My goal was not only to find bugs, but to evaluate the product from a UX, logic, and usability perspective.
Responsibilities included:
— exploratory testing of the mobile application
— identifying UI/UX, functional, and logical issues
— testing user flows and edge cases
— validating real-life usage scenarios
— creating detailed bug reports
— writing clear reproduction steps for developers
— recording screen videos demonstrating issues
— preparing structured QA reports in Notion based on the client/team workflow
— documenting bugs with screenshots, expected vs actual behavior, and additional notes
Because I also develop mobile apps myself, I understand the product from both the QA and developer side — including app logic, technical limitations, and how to communicate issues in a way that is actually useful for the development team.
The example below demonstrates both the structure of the full QA report and a detailed breakdown of one issue, including reproduction steps, expected/actual behavior, impact analysis, and visual references for the development team.
My goal was not only to find bugs, but to evaluate the product from a UX, logic, and usability perspective.
Responsibilities included:
— exploratory testing of the mobile application
— identifying UI/UX, functional, and logical issues
— testing user flows and edge cases
— validating real-life usage scenarios
— creating detailed bug reports
— writing clear reproduction steps for developers
— recording screen videos demonstrating issues
— preparing structured QA reports in Notion based on the client/team workflow
— documenting bugs with screenshots, expected vs actual behavior, and additional notes
Because I also develop mobile apps myself, I understand the product from both the QA and developer side — including app logic, technical limitations, and how to communicate issues in a way that is actually useful for the development team.
The example below demonstrates both the structure of the full QA report and a detailed breakdown of one issue, including reproduction steps, expected/actual behavior, impact analysis, and visual references for the development team.