| End-to-End (UI) |
Critical User Journeys: Buying a voucher, 'I'm Gifting' feature, multi-step online/offline redemption flow, checking voucher status, account management. |
Regression Suite: Covering core user flows post-deployment. Smoke Tests: Ensuring critical functionality works on new builds for every release. |
Reduced regressions in production, faster time-to-market for new features, improved user experience scores, fewer support tickets for core flows. |
| API/Service Layer |
Core Business Logic: Voucher creation, payment processing, instant digital delivery (SMS, Email, WhatsApp) APIs, 300+ brand integration points, offer application. |
API Contract Testing: Validating interactions with internal and external services (payment gateways, brand APIs). Data Validation: Ensuring voucher codes, PINs, and balances are correct post-transaction. |
Early detection of defects, improved integration stability, reduced reliance on slower UI tests, enhanced data integrity, faster feedback to developers. |
| Database Layer |
Data Integrity Checks: Verification of voucher states (redeemed, expired, active), transaction records, user accounts, and financial data consistency post-operations. |
Data Seed & Cleanup: Automated setup and teardown of test data. Validation Scripts: Ensuring consistency across linked systems (e.g., voucher balance after partial redemption). |
Prevention of data-related errors, reliable reporting, robust backend operations, reduced support tickets related to incorrect statuses. |
| CI Gates |
Build Verification Tests: Automated checks to ensure code merge doesn't break core functionality or introduce critical errors. Flaky Test Reduction: Mechanisms to identify and address unreliable tests. |
Pre-Commit Hooks & Post-Merge Checks: Integrating smoke and critical API tests into the CI/CD pipeline. Test Pyramid Implementation: Prioritizing fast, stable tests at lower layers. |
Faster feedback loops for developers, prevention of broken builds, stable deployment pipeline, increased release velocity, high confidence in code merges. |
| Negative Scenarios & Edge Cases |
Input Validations: Testing various valid/invalid inputs for voucher codes, PINs, contact details. Refund/Cancellation: Verifying refunds credited to original Gift Card balance. |
Parameterized Tests: Covering diverse data sets. Negative Testing: Validating error handling for invalid states ('invalid' or 'already redeemed' vouchers, store refusals, unreceived vouchers). |
Robustness against misuse, clearer error messages for users, reduced customer support load for common issues, enhanced system resilience. |