Stop 15 · Interview PreparationProcess & Strategy · 1/3

Test Strategy Scenario Questions

Part of the QA Testing Roadmap

In short

'How would you test this new feature?' has no single right answer. Interviewers want to see you think about risk, scope and time, instead of trying to test everything equally.

'How would you approach testing this new feature?' — testing whether you can design a structured test strategy from Phase 3, prioritizing based on risk rather than testing everything equally.

The purple blob as a cricket captain points fielders to their places on a green field.

Think of it like this

Setting the field as captain

A captain doesn't spread fielders evenly. If the batter loves the cover drive, two fielders go to cover. You place your testing effort the same way: more where the risk is highest.

Watch it happen

A structure for any 'how would you test X' question

Understand
Risks
Scope
Approach
Exit

1/5Ask about users, platforms, deadlines and what changed. Example: UPI payments added to a food app.

The big ideas

What you need to know

Risk-based

Rank features by impact and likelihood of failure. Money, data and login usually top the list.

Test levels

Say which risks you cover with unit, API, UI, manual exploratory and non-functional tests.

Time is limited

Always say what you'd do with one day versus one week. It shows you can prioritise.

Involve others

Mention talking to developers, product and support. Support tickets reveal real user pain points.

Save yourself the pain

Common mistakes

Oops

Jumping straight into a list of test cases.

Do this instead

Start with questions and risks. Cases come later, if at all, in a strategy answer.

Oops

Saying you'd test everything thoroughly.

Do this instead

Nobody has infinite time. Explain what you'd test first and what you'd consciously skip.

Your mission

Three scenarios, five minutes each

~25 min

Quick check

You have two days to test a new payment method before a big sale. What do you focus on first?

Go deeper

  1. 1Practice a repeatable structure: understand requirements, assess risk, design test approach.
  2. 2Prepare to discuss what you'd test first under limited time, and why.
  3. 3Practice explaining your reasoning process, not just presenting a final test plan.

More process & strategy at this stop

Stuck on this topic? Ask an Insider

Get 1:1 guidance from people who've walked this exact path — on the InsideEdge app.

Download
InsideEdge