// A BFSI test case — NEFT transfer
// Feature: Domestic fund transfer

// Test Case 1 — Valid transfer
// Steps:
// 1. Login with valid credentials
// 2. Navigate to Transfer > NEFT
// 3. Enter beneficiary account and IFSC
// 4. Enter amount: ₹10,000
// 5. Confirm with OTP
// Expected:
// - Success message with UTR
// - Debit from sender's account
// - Credit to beneficiary (T+0 for NEFT)

// Test Case 2 — Insufficient balance
// Expected:
// - Error: "Insufficient balance"
// - No debit from sender
// - No credit to beneficiary

// Test Case 3 — Invalid IFSC
// Expected:
// - Validation error at IFSC field
// - Transfer does not proceed

// Test Case 4 — Beneficiary not registered
// Expected:
// - Warning prompt: "Beneficiary not saved"
// - Option to add as one-time beneficiary

// Note: NEFT-specific assertions reflect
// real banking behavior — a QA tester who
// understands this is far more valuable
// than one who doesn't.

# Playwright + Pytest — login and transfer test
# tests/test_neft.py

import re
import pytest
from playwright.sync_api import Page, expect

@pytest.fixture
def app_url():
    return "https://demo-bank.example.com"

def test_login_succeeds(page: Page, app_url: str):
    page.goto(app_url)
    page.get_by_label("Username").fill("demo_user")
    page.get_by_label("Password").fill("demo_pass")
    page.get_by_role("button", name="Login").click()

    expect(page).to_have_url(re.compile("/dashboard"))
    expect(page.locator(".welcome")).to_contain_text("Welcome")

def test_neft_transfer_succeeds(page: Page, app_url: str):
    # Login
    page.goto(app_url)
    page.get_by_label("Username").fill("demo_user")
    page.get_by_label("Password").fill("demo_pass")
    page.get_by_role("button", name="Login").click()

    # Navigate to NEFT
    page.get_by_role("link", name="Fund Transfer").click()
    page.get_by_role("button", name="NEFT").click()

    # Fill beneficiary
    page.get_by_label("Beneficiary Account").fill("1234567890")
    page.get_by_label("IFSC").fill("HDFC0001234")
    page.get_by_label("Amount").fill("10000")

    page.get_by_role("button", name="Submit").click()

    # Confirm OTP (in a real test, use a test bypass)
    page.get_by_label("OTP").fill("123456")
    page.get_by_role("button", name="Confirm").click()

    # Assert success + UTR number shown
    expect(page.locator(".success-banner")) \
        .to_contain_text("Transfer successful")
    expect(page.locator(".utr-number")) \
        .to_have_text(re.compile(r"[A-Z0-9]{16}"))

# Note: this test is heavily simplified. Real BFSI
# tests cover dozens of edge cases — a genuine edge
# a bank employee can spot quickly.

# Python — verify ledger balances after a transfer
# (a critical BFSI QA check)

import pytest
import requests

BASE = "https://sandbox.example.com"

def test_ledger_balances_after_transfer(auth_headers):
    """
    After a transfer, the ledger must remain balanced:
    sum(credits) == sum(debits) for each account.
    """
    # Get yesterday's entries
    r = requests.get(
        f"{BASE}/ledger/entries?date=yesterday",
        headers=auth_headers,
    )
    entries = r.json()["entries"]

    by_account = {}
    for e in entries:
        acc = e["account_id"]
        by_account.setdefault(acc, {"credit": 0, "debit": 0})
        by_account[acc][e["type"]] += e["amount"]

    for acc, s in by_account.items():
        assert s["credit"] == s["debit"], (
            f"Unbalanced {acc}: "
            f"credit={s['credit']} debit={s['debit']}"
        )

# This is the kind of test a bank employee naturally
# thinks about — and a generic QA engineer often misses.
# This is your domain edge in action.

Project 1 — Manual test suite for a demo bank
1. Pick a public demo banking site
   (e.g., a sample onboarding or payments flow)
2. Write 30 test cases covering:
   - Login and session
   - Fund transfer (valid + invalid)
   - KYC steps
   - Statement download
3. Log 5 bugs with severity and financial impact
4. Publish as a PDF or on GitHub with screenshots

Why it works:
- Directly reflects BFSI QA work
- Shows domain-specific test design
- Easy for BFSI interviewers to review

Project 2 — Playwright automation for a banking flow
1. Automate login, transfer, and statement download
2. Use Playwright + Pytest with page objects
3. Add an assertion for UTR number format
4. Integrate into GitHub Actions CI
5. Record a 2-minute demo video

Why it works:
- Shows you can automate, not just click
- Pytest + page objects signal real framework discipline
- Trace + demo video prove real work

Weekly study plan (10-15 hours):
Mon 1.5h — Theory (manual testing or SQL)
Tue 1.5h — Practice on real test cases
Wed 1.5h — Theory (API or Playwright)
Thu 1.5h — Practice coding / scripts
Fri 1h   — Weekly review
Sat 3h   — Project work
Sun 2h   — Reading + rest

Consistency beats intensity.
Block study time like a bank schedule.

Job search plan (Month 6):
Week 1: Rewrite resume for QA roles
Week 2: LinkedIn + projects
Week 3: Apply to 10 roles per week
Week 4: 2 mock interviews
Week 5: Continue + reach out for referrals
Week 6: Iterate — refine answers, add demos

Aim for 8–12 quality applications per week.
Target BFSI-focused QA teams first —
your domain edge matters most there.