PT. Cazh Teknologi Inovasi (CARDS) · Purwokerto, Central Java, Indonesia

Sole QA engineer in a development team of five developers, two PMs, and one UI/UX designer; defining test coverage and bug reporting standards.

• Tested the CARDS ecosystem used by 700+ educational institutions - CARDS School (web dashboard), CARDS Parents, CARDS EDU, and Cazh POS together with its web dashboard on both Android and iOS - covering finance modules (student admissions, invoices, arrears, donations, savings, balance top-up and withdrawal) and the attendance module, as well as selected modules of the core banking system for BKD Pekalongan.
• Designed test scenarios and test cases for new and changed features, ran regression, UI, exploratory, and responsive testing across web, mobile, and POS platforms, and prepared and executed User Acceptance Testing scenarios before release.
• Built end-to-end automation in Cypress using the Page Object Model for the latest major releases: ~847 test cases across 64 spec files on CARDS School V3, and 86 test cases on the Cazh POS web dashboard (CPA V2).
• Designed the automation suite to stay traceable to the test case documentation, with every test carrying its own test case ID, using data-driven fixtures, cy.intercept for request and response verification, cy.session to avoid repeating login per test, and Mochawesome reporting.
• Validated incoming daily bug reports from the service team and other reporters: reproduced the findings, determined whether each was an actual defect, and explained the outcome back to the reporter.
• Performed bug hunting beyond documented test cases, both while testing specific features and during full sweeps across all products, then documented and tracked findings in Jira/Zephyr, Notion, and Google Sheets.
• Coordinated more than 60 QA interns: distributing test coverage, receiving their test reports, and deciding which findings were escalated to the development team.
• Reviewed interns' test cases and verified their bug reports so that anything reaching developers was valid and consistently formatted, while collaborating with Developers, PMs, and UI/UX in an Agile workflow.