Test Case Writing

Equivalence partitioning picks one input per class, boundary value analysis tests the edges, decision tables cover condition combinations, state transition testing covers legal and illegal moves, and pairwise testing covers all value pairs, so you get strong coverage with few cases and can justify every one.

Automate the repetitive, stable, business-critical, frequently run, data-driven, regression tests, and keep exploratory, one-off, volatile, and judgement-based checks manual, because automating unstable or low-value tests just builds a brittle, expensive suite nobody trusts.

Write the login test to open, navigate, fill, submit, and assert the dashboard, and make it robust with an environment base URL, externalized secrets, reused storage state, Playwright auto-waiting web-first assertions instead of sleeps, and explicit failed-login negative assertions.

Login testing beyond the happy path covers negatives, empty fields, masking, lockout, remember-me, session timeout, logout, injection and scripting attacks, password reset, browser and accessibility checks, and precise non-leaky error messages, because the interviewer is checking that you anticipate failure and abuse, not just success.

Payment testing prioritizes money correctness and reliability, declines, timeouts, duplicates, refunds, currency, and especially payment-succeeds-but-confirmation-fails, and idempotency keys matter more than UI validation because retries are routine and only idempotency stops a double charge.