Build the test cases from the acceptance criteria and the process flows, not from what got built. Get real users rather than project team proxies, use realistic data, and cover the exception paths, because that is where acceptance fails. Agree severity definitions and who makes the go or no go call in advance, so that argument does not happen on decision day.
Why interviewers ask this
Interviewers want to see that you connect requirements through to acceptance rather than handing testing off. They listen for cases derived from criteria, which is where traceability earns its keep, for real users and realistic data, and for defect severity and go or no go authority agreed beforehand. That last point is the one candidates skip and the one that causes genuine chaos on real projects.
How to structure your answer
- Derive test cases from acceptance criteria, not from the build.
- Use real users rather than project team proxies.
- Insist on realistic data, including messy records.
- Agree severity definitions and the go or no go owner in advance.
- Use traceability to find requirements with no test.
Example answer
I build the cases from the acceptance criteria and the process flows, so we are testing what the business asked for rather than what got built, and that is where traceability pays for itself, because I can see quickly which requirements have no test against them. Then I want actual users, not a proxy from the project team, because the project team knows how it is supposed to work and unconsciously avoids the awkward paths. Realistic data matters just as much; a clean test dataset will pass things that fall over on the first real record with a missing field. The part people skip is agreeing the rules up front: what counts as critical, high and medium, and who makes the go or no go call. Having that agreed two weeks before means decision day is about facts rather than about who gets to decide.
Walking into this interview soon? GhostPilot listens to your live call, spots the question the moment it is asked, and puts a structured answer on your screen in real time. Try it on your next mock, or grab a $29 Session Pass, no subscription, for the real thing.
See how it worksFollow-up questions to expect
- What do you do when users will not make time for acceptance testing?
- How do you handle a critical defect found the day before go live?
- How is acceptance testing different when the delivery is iterative?
Related business analyst questions
Your interviewer will ask their own version of this. Paste your actual job description into the free Question Predictor and get the 20 questions that role is most likely to ask, with what each one is really probing.
Predict my questions