Arya Bank NetBanking — UI test results

Fictional bank, synthetic data. Playwright + TypeScript suite (Page Objects, axe-core WCAG 2.2, visual regression, network mocking) on desktop and mobile browsers, run once against the clean app and once per planted UI bug.

Clean app
325/325
test runs pass on 5 browser projects
Planted UI bugs caught
9/9
none escaped
Every bug on
105
of 325 test runs fail
Browsers
5
chromium, firefox, webkit, mobile-chrome, mobile-safari

Reports

Allure report — clean appAllure, with run-to-run trendAllure report — every bug onAllure, every planted bug onPlaywright report — clean apptraces, screenshots, stepsPlaywright report — every bug ontraces, screenshots, steps

Planted UI bugs

A bug counts as caught when at least one test fails with only that bug switched on.

BugDefectResultTests that caught it
UI-01 Confirm button has no accessible name
Icon-only Confirm on the transfer review; a screen reader announces just "button".
 ✓ caught
Accessibility, Visual, Network, E2E
  • Accessibility transfer review step (chromium, firefox, mobile-chrome)
  • Accessibility a transfer can be completed with the keyboard only (chromium, firefox)
  • E2E a new transfer shows up in the statement (chromium, firefox, mobile-chrome)
  • E2E transfer with paise: review, confirm, and the exact amount leaves the account (chromium, firefox, mobile-chrome)
  • … and 7 more
UI-02 Login error text fails contrast
Light grey error message on white (about 1.9:1); hard to read for low-vision users.
 ✓ caught
Accessibility
  • Accessibility login page showing an error (chromium, firefox, mobile-chrome)
UI-03 Paise dropped from the amount
1500.75 is sent as 1500: the customer pays a different amount than they typed.
 ✓ caught
Accessibility, E2E
  • Accessibility a transfer can be completed with the keyboard only (chromium, firefox)
  • E2E a new transfer shows up in the statement (chromium, firefox, mobile-chrome)
  • E2E transfer with paise: review, confirm, and the exact amount leaves the account (chromium, firefox, mobile-chrome)
UI-04 Mobile layout overflow
Below 600px the account cards are fixed at 520px wide; the page scrolls sideways and Transfer is pushed off-screen.
 ✓ caught
Visual, Responsive, E2E
  • E2E quick action "Download statement" opens the right page (mobile-chrome)
  • Responsive /dashboard has no sideways scrolling (mobile-chrome)
  • Responsive dashboard quick actions are fully on screen (mobile-chrome)
  • Visual dashboard (mobile-chrome)
UI-05 Double submit on Confirm
Confirm stays enabled and each click sends a new request: a double tap pays twice.
 ✓ caught
Network, E2E
  • E2E double-clicking Confirm sends the money once (chromium, firefox, mobile-chrome)
  • E2E Confirm is disabled while the transfer is being sent (chromium, firefox, mobile-chrome)
  • Network retry after a failure uses the same idempotency key, so the money moves once (chromium, firefox, mobile-chrome)
UI-06 Failed transfer shown as success
When the transfer API errors or the network drops, the page still says "Transfer successful".
 ✓ caught
Network, E2E
  • E2E insufficient funds: clear error and no money moves (chromium, firefox, mobile-chrome)
  • Network transfer API returns 500: error shown, no success screen, no money moves (chromium, firefox, mobile-chrome)
  • Network network drops during transfer: customer is told nothing was sent (chromium, firefox, mobile-chrome)
  • Network retry after a failure uses the same idempotency key, so the money moves once (chromium, firefox, mobile-chrome)
UI-07 Beneficiary form has no labels
Inputs use placeholder text only; screen readers can't name the fields.
 ✓ caught
Accessibility, E2E
  • Accessibility every form field has a visible label (placeholders are not labels) (chromium, firefox, mobile-chrome)
  • E2E add a beneficiary using the labelled form, then pay them (chromium, firefox, mobile-chrome)
  • E2E invalid account number and IFSC are flagged on the right fields (chromium, firefox, mobile-chrome)
  • E2E an existing beneficiary can't be added twice (chromium, firefox, mobile-chrome)
UI-08 Logout keeps the session
Logout only redirects; the session cookie stays valid and /dashboard opens again.
 ✓ caught
E2E
  • E2E logout ends the session: the dashboard no longer opens (chromium, firefox, mobile-chrome)
UI-09 Statement uses a Chromium-only API
navigator.userAgentData is undefined in Firefox and Safari, so the statement never loads there.
 ✓ caught
Accessibility, Network, E2E
  • Accessibility statement (firefox)
  • E2E default view: salary account from 1 Sep to today (firefox)
  • E2E September only: right rows and totals (firefox)
  • E2E range boundaries are inclusive (firefox)
  • … and 4 more

Updated 2026-10-17 00:30 UTC · Source on GitHub