How would you decide what to test, and at which layer, when planning the test strategy for a new payment-checkout feature?

technical-conceptual · Mid level · software-engineering

What the interviewer is really asking

Assesses whether the candidate can build a risk-driven, layered test strategy that targets coverage where defects and impact concentrate, rather than testing everything uniformly.

What to say

What to avoid

Example answers

Strong: For a checkout feature I ranked flows by risk and impact: the charge-and-create-order path was tier 1, so I covered discount and tax math in unit tests, the payment-provider call and order write in integration tests against a sandbox, and kept just two E2E journeys (successful purchase, declined card). Lower-risk flows like changing a saved address got integration coverage only. I wrote down the release bar — all tier-1 scenarios green, zero open sev-1 — before we started.

Weak: I'd write tests for every screen and field in the feature so we have full coverage, and run them all through the UI to be safe.

Want questions matched to your role? Paste a job title, job description, or CV and get a personalized set, or go Pro to unlock the full bank.