Skip to content
RED SAGSkills
mediumQA Engineer interview question

You are given a new "split payment" feature in a payments app. How would you create a test plan?

What the interviewer wants to hear

  • Understand requirements and clarify open questions
  • Define scope, out of scope and risks
  • Identify test types: functional, integration, negative, security, performance
  • Plan test data, environments and devices
  • Entry and exit criteria, schedule and reporting

Model answer

First I read the stories and meet the product owner and developers to clarify rules: how many people can split, can amounts be unequal, what happens if one person does not pay, and refund behaviour. Then I write the plan. Scope includes creating a split, inviting users, partial payment, reminders, cancel and refund; out of scope might be international currencies. I list risks, with money accuracy and rounding at the top, then concurrent payments and notification failures. Test types: functional, negative cases like amounts that do not add up, integration with the payment gateway and bank callbacks, security such as one user changing another's share, basic load on busy days, and accessibility. I plan test data, sandbox accounts and devices. Entry criteria: build passes smoke tests. Exit criteria: no open critical bugs and all high-risk tests passed. I share daily progress.

Can you answer it under time pressure?

Take a timed medium round and get scored on every answer.

Start mock interview

More medium QA Engineer questions