Question 1

Test a registration form (name, email, password, confirm password, submit).

Accepted Answer

Questions first: password policy? email verification? platforms? Then: EP/BVA per field (lengths, allowed characters), password/confirm mismatch, registering an existing email (proper error without user enumeration), empty fields, clarity of error messages, password masking, injection attempts, post-registration behaviour (email, auto-login?), double-submit, button disabling on slow networks. Priority: happy path + existing email + validation.

Question 2

Requirement: "A discount coupon applies only to the first order." Build the test scenarios.

Accepted Answer

Positive: new user + coupon → discount applied. Negative: same coupon on second order → rejected with a clear message. Edge: does a cancelled first order still count as "first"? (a requirements question!); coupon applied but payment failed — is it "used"? Two parallel first orders from two devices (race condition); guest checkout + later registration; coupon enforced at API level (hiding it in the UI is not enough).

Question 3

The interviewer disagrees with your answer and pushes back — how do you behave?

Accepted Answer

This is often a stress test. I justify my position but genuinely listen to the counter-argument — if they're right, I openly accept it ("true, my approach would fail in that case"). Neither stubborn defence nor instant surrender is a good signal; the goal is showing calm, fact-based discussion.

Practical tasks: "How would you test this?"