Deskripsi Pekerjaan
Informasi lengkap tentang posisi dan persyaratan
Ringkasan Yukerja
Lowongan Quality Assurance di PCS Payment kami kurasi dari Glints (kategori Teknologi & IT). Perhatikan lokasi kerja (Kapanewon Mlati) sebelum melamar. Yukerja.com bukan pemberi kerja — lamaran diproses di situs sumber resmi.
Qualifications and Experience:
- Minimum experience 2–4 years as QA Engineer, QA Analyst, or SDET in Fintech, E-Wallet, PPOB, Payment Gateway, or POS industries.
- Solid understanding of digital payment ecosystems including PPOB (Payment Point Online Bank), POS (Point of Sale) systems, and merchant management. Familiar with common transaction flows (inquiry, payment, callback, settlement, reconciliation) and API integrations.
- Proficient in both manual and automated testing. Able to design test cases, execute UAT with end-users, and produce structured evidence.
- Comfortable working with AI-generated test cases. Able to critically validate, refine, and supplement AI output — not blindly accept. Willing to learn and adopt new AI tools rapidly.
- Proficient in API testing tools (Postman or equivalent), familiar with version control (Git), test management tools, and able to work with .md documentation workflow. Experience with automation frameworks (Selenium, Cypress, Playwright, or API automation) is a plus.
- Able to operate in fast-paced environment with frequent scope changes. Comfortable re-prioritizing test coverage on short notice when requirements shift mid-sprint.
Job Description:
- Receive Impact Analysis Document, design comprehensive test scenarios covering happy path, edge cases, negative cases, and integration points.
- Execute manual testing for critical transactional flows where automated validation is insufficient.
- Leverage AI-generated test cases as baseline. Validate completeness, add domain-specific scenarios, and refine coverage. Critically assess AI output rather than accept without review.
- Collaborate with PO during UAT sessions. Provide technical support when users encounter issues, help reproduce bugs, and ensure test evidence is properly documented.
- Document defects with clear reproduction steps, expected vs actual results, severity classification, and supporting evidence (logs, screenshots, API traces).
- Maintain and expand regression test suite. Identify repetitive manual tests that can be automated. Continuously improve test efficiency without sacrificing coverage.