Skip to content
ISTQB
All coursesPlacement Report
‹ Back to previous sectionCourse homeAll page URLs

Test Analyst Interview Questions & Answers

40 questions for Test Analyst interviews — 4 easy, 30 medium, 6 hard.

About the Test Analyst role

Test analysts own test analysis and design for a module or product. They apply decision tables, state transition models and risk-based prioritisation to build efficient test suites, maintain traceability to requirements, and guide junior testers. Many go on to the ISTQB Advanced Test Analyst certification. The role suits testers with two to five years of experience who enjoy business logic and domain depth.

Test design techniques Traceability Risk-based testing Domain knowledge Test data design
Solved for this roleStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
3 questions free Unlock the rest in seconds
01

How do you report test status to non-technical stakeholders?

Managing the Test ActivitiesMedium
Save to ▾
Show answer
I focus on decisions they need to make. I use a short dashboard: overall status in plain words, coverage of key requirements, open critical defects and their business impact, top risks with mitigation, and what is needed from them. I avoid jargon, use simple charts and trends, and keep detailed data available for anyone who wants it. Different audiences may need different levels of detail.
02

What is branch testing and how is branch coverage measured?

White-Box, Experience and Collaboration-Based TestingMedium
Save to ▾
Show answer
A branch is a transfer of control between two nodes in the control flow graph. Branches can be unconditional, like straight-line code, or conditional, like the true and false outcomes of an if or the cases of a switch. Branch coverage = branches exercised / total branches x 100. Branch testing designs tests so that every branch, including the hidden false path of an if without else, is exercised.
03

Why does 100 percent branch coverage guarantee 100 percent statement coverage, but not the other way round?

White-Box, Experience and Collaboration-Based TestingMedium
Save to ▾
Show answer
Every statement lies on at least one branch, so exercising all branches executes all statements. The reverse fails when a decision has an empty outcome. Example: 'if x > 10: print(big)' followed by 'print(done)'. One test with x = 15 runs every statement, giving 100 percent statement coverage, but the false branch is never taken, so branch coverage is only 50 percent. This is called subsumption.
04

Calculate a three-point estimate where optimistic is 6, most likely is 9 and pessimistic is 18 person-days.

Managing the Test ActivitiesMedium
Save to ▾
Show answer
E = (a + 4m + b) / 6 = (6 + 4 x 9 + 18) / 6 = (6 + 36 + 18) / 6 = 60 / 6 = 10 person-days SD = (b - a) / 6 = (18 - 6) / 6 = 2 Report the estimate as 10 +/- 2 person-days, which gives a range of 8 to 12.
05

What is the difference between 2-value and 3-value boundary value analysis?

Black-Box Test TechniquesMedium
Save to ▾
Show answer
BVA applies to ordered partitions. In 2-value BVA each boundary has two coverage items: the boundary value and its closest neighbour in the adjacent partition. In 3-value BVA there are three: the boundary and both neighbours. For a valid range 18 to 60, 2-value gives 17, 18, 60, 61, and 3-value gives 17, 18, 19, 59, 60, 61. 3-value is stricter and can catch defects like 'x == 18' written instead of 'x >= 18'.
06

What is the difference between a test progress report and a test completion report?

Managing the Test ActivitiesMedium
Save to ▾
Show answer
A test progress report is produced regularly during testing, for example daily or per sprint. It covers the period, progress against plan, impediments, metrics, new or changed risks and planned work. A test completion report is prepared at the end of a test level, iteration or project. It summarises testing, evaluates quality against the plan, lists deviations, unmitigated risks, open defects, metrics and lessons learned.
07

Tell me about an exploratory testing session that found a critical defect.

White-Box, Experience and Collaboration-Based TestingMedium
Save to ▾
Show answer
Situation: a ticket booking app had passed all scripted tests. Task: run a one-hour exploratory session on seat selection. Action: I tried quick double taps, switching networks and booking the same seat from two devices. Result: two users could book the same seat. I logged a detailed report with videos, it was fixed before release, and concurrency tests were added to the regression suite.
08

What is the value of white-box testing?

White-Box, Experience and Collaboration-Based TestingMedium
Save to ▾
Show answer
White-box testing considers the whole implementation, so it can find defects even when the specification is vague, outdated or incomplete. Coverage gives an objective measure of thoroughness. It can also be used in static testing, for example dry runs of code or pseudocode. Its main weakness is that it cannot detect omissions: if a requirement was never implemented, no white-box test will notice it.
09

Discount depends on customer type (regular, gold, platinum) and whether the order exceeds 1,000 rupees. How many rules does the full decision table have?

Black-Box Test TechniquesMedium
Save to ▾
Show answer
When conditions are not Boolean, multiply the number of values of each condition. Customer type has 3 values and the order condition has 2, so the full table has 3 x 2 = 6 rules. Each rule becomes one test case for 100 percent decision table coverage. If, for example, platinum always gets the same discount regardless of amount, those two columns can be merged, giving 5.
10

Tell me about a time a review you did prevented a serious problem.

Static TestingMedium
Save to ▾
Show answer
Situation: reviewing a refund user story, I noticed it did not say how partial refunds work on discounted orders. Task: clarify it before development started. Action: I logged the gap, set up a 15-minute call with the product owner and developer, and we added three acceptance criteria with worked examples. Result: the feature shipped without the refund calculation errors that had hurt an earlier release.
11

Tell me about a time a test design technique helped you find a defect.

Black-Box Test TechniquesMedium
Save to ▾
Show answer
Situation: I was testing a scholarship form where students aged 17 to 25 were eligible. Task: design efficient tests for the age rule. Action: I applied boundary value analysis and tested 16, 17, 25 and 26. Result: 25 was wrongly rejected because the code used 'less than 25'. The developer fixed it, and I shared the BVA checklist with the team so others used it too.
12

How would you combine test techniques for a new UPI payment feature?

White-Box, Experience and Collaboration-Based TestingHard
Save to ▾
Show answer
I would use black-box techniques: EP and BVA for amount limits, decision tables for rules such as daily limits and first-time payee checks, and state transitions for payment status from initiated to success, failed or pending. Developers would add white-box branch coverage in unit tests. I would add error guessing and exploratory sessions on network drops, duplicate taps and timeouts, prioritised by risk.
13

Describe a situation where a developer rejected your defect. How did you handle it?

Fundamentals of TestingMedium
Save to ▾
Show answer
Situation: a developer marked my defect 'works as designed'. Task: resolve it without conflict. Action: I re-read the user story, attached the acceptance criteria that contradicted the behaviour, and discussed it calmly with the developer and product owner, focusing on user impact rather than blame. Result: the product owner confirmed it was a defect, and we clarified the story wording so similar confusion did not happen again.
14

An amount field accepts 0.01 to 999.99 with two decimal places. What are the 2-value boundary values?

Black-Box Test TechniquesHard
Save to ▾
Show answer
The closest neighbour depends on the precision, here 0.01. Lower boundary: 0.00 (invalid) and 0.01 (valid). Upper boundary: 999.99 (valid) and 1000.00 (invalid). So the four test values are 0.00, 0.01, 999.99 and 1000.00. Always confirm the precision from the specification, because with whole numbers the neighbour would be 1, and with three decimals it would be 0.001.
15

A developer says one value per partition is enough. Why might you still add boundary tests?

Black-Box Test TechniquesMedium
Save to ▾
Show answer
Equivalence partitioning assumes all values in a partition behave the same, but many defects occur at the edges, where developers write '>' instead of '>=' or use the wrong limit. One middle value like 35 in an 18 to 60 range will never reveal these. Boundary value analysis adds tests at 17, 18, 60 and 61, so the two techniques together give good coverage with few tests.
16

You identified 6 equivalence partitions and your tests exercise 4 of them. What is the coverage? Does adding a second test in the same partition help?

Black-Box Test TechniquesHard
Save to ▾
Show answer
EP coverage = exercised partitions / identified partitions x 100 = 4 / 6 x 100 = 66.7 percent. Adding another test in an already covered partition does not increase coverage, because coverage counts partitions, not tests. To reach 100 percent you need tests in the two missing partitions. Exams often include such distractors to see if you count tests instead of coverage items.
17

How does decision table testing work, and how is coverage measured?

Black-Box Test TechniquesMedium
Save to ▾
Show answer
Decision tables model combinations of conditions and the resulting actions, which suits business rules. Each column is a rule: one combination of conditions with its actions. With n Boolean conditions, a full table has 2 to the power n columns. Coverage items are the feasible columns, so coverage is exercised columns divided by feasible columns. Tables can be minimised by merging columns where a condition does not affect the outcome, shown with a dash.
18

Derive test conditions for the requirement 'Users can transfer up to 50,000 rupees per day.'

Fundamentals of TestingMedium
Save to ▾
Show answer
Read the test basis and list testable aspects. Conditions: a transfer within the limit succeeds; a transfer of exactly 50,000 succeeds; a transfer above 50,000 is rejected with a clear message; several transfers in one day are added together against the limit; the limit resets the next day; zero or negative amounts are rejected. Prioritise them by risk, then design test cases with exact amounts using boundary value analysis.
19

Explain collaborative user story writing, the 3 Cs and INVEST.

White-Box, Experience and Collaboration-Based TestingMedium
Save to ▾
Show answer
User stories are written collaboratively by business, development and testing. The 3 Cs are Card (the medium describing the story), Conversation (how the story will be used, documented or verbal) and Confirmation (the acceptance criteria). A good story follows INVEST: Independent, Negotiable, Valuable, Estimable, Small and Testable. If stakeholders cannot say how to test a story, it is probably unclear or does not reflect real value.
20

A field accepts integers from 1 to 99. Which set of values achieves 100 percent 2-value BVA coverage: {1, 99}, {0, 1, 99, 100}, {0, 50, 100} or {1, 2, 98, 99}?

Black-Box Test TechniquesEasy
Save to ▾
Show answer
The answer is {0, 1, 99, 100}. Two-value BVA needs each boundary value and its closest neighbour in the adjacent partition: 0 and 1 at the lower edge, 99 and 100 at the upper edge. {1, 99} misses the invalid neighbours, {0, 50, 100} misses 1 and 99, and {1, 2, 98, 99} stays inside the valid partition, which is closer to 3-value thinking.
21

Build a decision table for a loan rule: approve if salary is at least 30,000 and credit score is at least 700; refer if only one is met; otherwise reject.

Black-Box Test TechniquesMedium
Save to ▾
Show answer
Conditions R1 R2 R3 R4 Salary >= 30000 T T F F Score >= 700 T F T F Actions Approve X - - - Refer to officer - X X - Reject - - - X Two Boolean conditions give 2 x 2 = 4 rules, so 4 test cases give 100 percent decision table coverage.
22

How does a tester contribute to release and iteration planning?

Managing the Test ActivitiesMedium
Save to ▾
Show answer
In release planning, testers help write testable user stories and acceptance criteria, take part in product and quality risk analyses, estimate test effort for stories, define the test approach and plan release testing. In iteration planning, they join detailed risk analysis of stories, check testability, break stories into testing tasks, estimate testing effort and identify the functional and non-functional aspects to test.
23

Which test estimation techniques are described in CTFL v4.0?

Managing the Test ActivitiesMedium
Save to ▾
Show answer
Estimation based on ratios uses historical figures, such as a development-to-test effort ratio. Extrapolation uses measurements from the current project, for example averaging the last three iterations. Wideband Delphi is an expert-based technique where experts estimate separately and iterate until consensus; Planning Poker is an Agile variant. Three-point estimation uses optimistic, most likely and pessimistic values to calculate a weighted estimate and its standard deviation.
24

A field accepts integers from 5 to 15. List the 3-value BVA test values.

Black-Box Test TechniquesMedium
Save to ▾
Show answer
In 3-value BVA, each boundary gives the boundary value plus both neighbours. Lower boundary 5 gives 4, 5 and 6. Upper boundary 15 gives 14, 15 and 16. So the six values are 4, 5, 6, 14, 15 and 16. Compared with 2-value BVA (4, 5, 15, 16), the extra values 6 and 14 help detect mistakes in comparison operators inside the range.
25

Model an ATM PIN entry with three attempts as states and transitions. How many tests are needed for valid transitions coverage?

Black-Box Test TechniquesHard
Save to ▾
Show answer
States: Idle, WaitPIN, Try2, Try3, Access, Locked Idle --insert card--> WaitPIN WaitPIN --correct PIN--> Access WaitPIN --wrong PIN--> Try2 Try2 --correct PIN--> Access Try2 --wrong PIN--> Try3 Try3 --correct PIN--> Access Try3 --wrong PIN--> Locked There are 7 valid transitions. Access and Locked are final states, so each test ends there; covering all 7 needs at least 4 tests.
26

What happens in test monitoring, test control and test completion?

Managing the Test ActivitiesMedium
Save to ▾
Show answer
Test monitoring gathers information about testing to check progress and whether exit criteria are met, using metrics like test case progress, defect counts, coverage and cost. Test control uses that information to give guidance and corrective actions, such as reprioritising tests or changing the schedule. Test completion collects data from finished activities to consolidate experience, testware and other information, usually at milestones like release or end of iteration.
27

Free shipping applies for orders of 499 rupees or more, otherwise a fee of 40 applies. Design tests using EP and BVA.

Black-Box Test TechniquesMedium
Save to ▾
Show answer
Partitions: 0 or less is invalid, 1 to 498 pays 40, and 499 or more ships free. EP tests: 0 rejected, 250 pays 40, 800 free. 2-value BVA adds 0 and 1 at the lower edge and 498 and 499 at the free shipping boundary. Combined minimal set: 0, 1, 250, 498, 499 and 800, each with the expected fee clearly stated.
28

What test case prioritisation strategies are there?

Managing the Test ActivitiesMedium
Save to ▾
Show answer
Risk-based prioritisation orders tests by the results of risk analysis, running tests for the highest risks first. Coverage-based prioritisation orders by coverage, running tests that achieve the most coverage first; additional coverage prioritisation picks each next test by the extra coverage it adds. Requirements-based prioritisation follows the priorities of requirements set by stakeholders. Dependencies can force a lower-priority test to run first.
29

The product owner writes vague acceptance criteria such as 'search should work well'. What do you do?

White-Box, Experience and Collaboration-Based TestingMedium
Save to ▾
Show answer
I would suggest a short three-amigos session with the product owner and a developer. Together we would turn the vague criterion into testable ones, for example 'searching by product name returns matching items sorted by relevance', 'no results shows a helpful message' and 'results load in under 2 seconds'. Writing them as Given/When/Then scenarios makes them clear and ready for ATDD.
30

A quantity field accepts 1 to 100. List the 2-value BVA test values.

Black-Box Test TechniquesEasy
Save to ▾
Show answer
The valid partition is 1 to 100, with invalid partitions below and above it. For each boundary, take the boundary and its closest neighbour in the adjacent partition. Lower boundary: 0 and 1. Upper boundary: 100 and 101. So 2-value BVA needs four values: 0, 1, 100 and 101, and four test cases give 100 percent 2-value boundary coverage.
31

What is statement testing and how is statement coverage calculated?

White-Box, Experience and Collaboration-Based TestingEasy
Save to ▾
Show answer
Statement testing designs tests that execute the executable statements in the code. Statement coverage = statements executed by the tests / total executable statements x 100. Reaching 100 percent means every executable statement ran at least once, so a defect in any statement may be triggered. However, it does not guarantee that all decision logic is tested, for example the false outcome of an if without an else.
32

How many tests are needed for full statement and branch coverage of this nested code?

White-Box, Experience and Collaboration-Based TestingMedium
Save to ▾
Show answer
if a > 0: if b > 0: s1 else: s2 else: s3 Statement coverage needs 3 tests, because s1, s2 and s3 are on different paths. Branch coverage also needs 3: (a > 0, b > 0), (a > 0, b <= 0) and (a <= 0). With full if-else structures, both criteria need the same number of tests.
33

Your CI pipeline takes two hours because most automated tests are UI tests. What do you suggest?

Managing the Test ActivitiesMedium
Save to ▾
Show answer
The suite looks like an inverted test pyramid. I would push checks down: move business logic checks to unit tests, cover service rules with API tests, and keep only a small set of end-to-end UI tests for critical user journeys. I would also run tests in parallel and split suites into a fast smoke stage and a fuller nightly run. Feedback becomes faster and tests less flaky.
34

Payment type has 3 partitions (card, UPI, wallet) and customer type has 2 (new, existing). What is the minimum number of tests for Each Choice coverage?

Black-Box Test TechniquesMedium
Save to ▾
Show answer
Each Choice coverage needs every partition from each input used at least once, and one test can cover one partition of each input at the same time. So the minimum equals the largest number of partitions: 3. Example tests: card with new, UPI with existing, wallet with new. Covering all combinations would need 3 x 2 = 6 tests, which is not required for Each Choice.
35

A new tester has no domain knowledge and no detailed test cases. How can checklists help, and what is the risk?

White-Box, Experience and Collaboration-Based TestingMedium
Save to ▾
Show answer
A checklist of high-level conditions, such as validations, error messages, navigation and security basics, gives the new tester structure and consistency while learning the domain. Each run can vary slightly, which increases coverage. The risk is that checklists wear out as developers learn to avoid listed defects, so the team should update them with new defect patterns and pair the tester with an experienced colleague.
36

What is risk, and how do project risks differ from product risks?

Managing the Test ActivitiesEasy
Save to ▾
Show answer
A risk is a potential event or condition whose occurrence causes an adverse effect. Risk level is determined by likelihood and impact. Project risks affect the management and control of the project, such as staff shortages, delays, budget cuts, vendor problems or tool issues. Product risks relate to quality characteristics of the product, such as missing functionality, wrong calculations, slow response, poor security or bad usability.
37

Why is not every failed test a defect in the software?

Defect and Configuration ManagementMedium
Save to ▾
Show answer
A failure can be caused by the test itself or the environment, not the test object. Common causes include wrong expected results, outdated test data, incorrect test scripts, misconfigured environments, network issues or unavailable third-party services. CTFL v4.0 therefore talks about anomalies, which are analysed before being reported as defects. Logging every failure as a defect without analysis creates false positives and wastes developer time.
38

Your tests achieved 100 percent branch coverage, yet users reported a defect. How is that possible?

White-Box, Experience and Collaboration-Based TestingMedium
Save to ▾
Show answer
Coverage shows which code was executed, not that the code is correct or complete. The defect may come from a missing requirement that was never coded, which white-box testing cannot detect; from specific data values not used in tests; from integration or environment issues; or from wrong expected results. Coverage is a useful measure of thoroughness, but it must be combined with black-box and experience-based techniques.
39

A key tester resigns and a vendor will deliver a module late. How do you treat these risks?

Managing the Test ActivitiesHard
Save to ▾
Show answer
Both are project risks. For the resignation, I would mitigate by documenting knowledge, pairing another tester for a handover and adjusting assignments; a contingency plan could be a short-term contractor. For the vendor delay, I would monitor delivery dates, prepare stubs to test our side, reorder testing to start other modules first and agree a contingency with management.
40

A decision table has three Boolean conditions. If condition A is false, the result is always 'reject'. How many columns does the minimised table have?

Black-Box Test TechniquesHard
Save to ▾
Show answer
A full table has 2 to the power 3 = 8 columns. When A is false, the other two conditions do not matter, so those four columns merge into one column with dashes for B and C. When A is true, the four combinations of B and C remain. The minimised table has 4 + 1 = 5 columns, so 5 tests give full coverage, if all columns are feasible.

Frequently asked questions

What does a Test Analyst do?

Test analysts own test analysis and design for a module or product. They apply decision tables, state transition models and risk-based prioritisation to build efficient test suites, maintain traceability to requirements, and guide junior testers. Many go on to the ISTQB Advanced Test Analyst certification. The role suits testers with two to five years of experience who enjoy business logic and domain depth.

Which skills are tested in a Test Analyst interview?

Expect questions on Test design techniques, Traceability, Risk-based testing, Domain knowledge, Test data design. Most rounds also ask you to explain a project and solve one practical problem live.

How do I prepare for a Test Analyst interview?

Revise Black-Box Test Techniques, White-Box, Experience and Collaboration-Based Testing, Managing the Test Activities first using the topic sheets, practise the questions on this page aloud, then do one full mock interview to practise timing.

Topic sheets for this role

Black-Box Test Techniques questionsWhite-Box, Experience and Collaboration-Based Testing questionsManaging the Test Activities questions

Other roles

Manual Test EngineerQA AnalystAgile QA EngineerTest LeadTest Manager

More ways to practise

Company-wise ISTQB questionsExperience-wise ISTQB questionsRole-wise ISTQB questionsCity-wise ISTQB questionsMost asked ISTQB questionsScenario-based questionsPractical / hands-on questionsHR & behavioural questionsISTQB mock interviewOnline assessment questionsTechnical round questionsManagerial round questionsISTQB topic sheets