Home/QA case studies/5 of 6
MTR is a flexible savings plan with automatic monthly deductions (IDR/USD, 1–20 year tenors, free life insurance). This project tested enhancements requiring regression testing to ensure existing functionality remained intact.
4 sample test cases2 pass2 fail3 bugs found
Note: all test cases and bug reports in this portfolio are illustrative samples reconstructed from memory after leaving Bank Mandiri. Original documents were stored in Jira, accessible only via the internal Bank Mandiri network. Feature names, flows, and defect types reflect actual work performed; sensitive internal data has been anonymized.
Four cases, including a regression check after deployment.
Scroll the table sideways to see every column.
| TC ID | Status | Test scenario | Test steps | Expected result | Actual result | Priority |
|---|---|---|---|---|---|---|
| TC-MTR-01 | PASS | Create MTR in IDR with monthly setoran Rp 500.000 |
| MTR created; record in DB with correct amount, currency, tenor, and ACTIVE status | MTR created and all fields saved correctly in database | High |
| TC-MTR-02 | FAIL | Create MTR in USD with monthly setoran USD 10 |
| MTR USD created; record saved with currency = USD and amount = 10 | MTR created with USD currency but amount saved as IDR equivalent in DB | High |
| TC-MTR-03 | FAIL | MTR account display for frozen account status |
| Page shows frozen account message; actions (top-up, cancel) are disabled | Page shows frozen status but Top Up button remains active and tappable | Medium |
| TC-MTR-04 | PASS | Regression: existing MTR auto-debit still executes after enhancement deployment |
| Pre-existing auto-debit continues to execute on schedule without interruption | Pre-existing auto-debit executed correctly after enhancement deployment | High |
Three sample bug reports, as written for the development team.
ExpectedAmount = 10, currency = USD.
ActualAmount = 160000 (IDR equivalent), currency = USD — data mismatch causes incorrect auto-debit.
Priority: High
ExpectedTop Up button disabled/hidden per PO requirement for frozen accounts.
ActualTop Up button remains enabled; tapping initiates transaction flow.
Priority: Medium
ExpectedCurrent month label (e.g., July 2026).
ActualMonth label shifted by 1; shows June 2026 for July transactions.
Priority: Low
One query to validate the data, one to track the defects.
SELECT mtr_id, account_id, currency, amount, tenor_years, status FROM mtr_accounts WHERE mtr_id = 'MTR-000045';
Confirms BUG-MTR-01: the USD amount was stored as its IDR-equivalent value (160000) instead of the original amount (10), which would cause incorrect future auto-debit deductions.
project = "LIVIN" AND component = "MTR" AND issuetype = Bug AND status IN ("Open", "In Progress", "Reopened") ORDER BY priority DESC, created ASC
Tracks open defects for the MTR enhancement, prioritizing the currency conversion issue (BUG-MTR-01) ahead of lower-severity UI bugs.
About the SQL. The query is an illustrative example reconstructed to show the type of database validation performed during testing. Table and column names have been generalized and anonymized and do not reflect the actual production schema. It uses SQLite syntax as a lightweight, portable reference; the same logic applies on MySQL or PostgreSQL with minor syntax adjustments.
About the JQL. It uses Jira's real query language and reflects the kind of filter commonly used for defect tracking. The project key ("LIVIN") and component name are illustrative. JQL filters and sorts issues; for counts by status or component, the filter is combined with Jira's "Group By" option or a dashboard gadget.