ISTQB Foundation Practice Test

ISTQB Certified Tester Foundation Level (CTFL)

ISTQB Foundation overview

  • 200 practice questions
  • 32 flashcards
  • 6 study guide topics
  • 40 key terms

What you'll study

  • Fundamentals of Testing17%
  • Testing Throughout the Software Development Lifecycle17%
  • Static Testing17%
  • Test Techniques17%
  • Test Management16%
  • Tool Support for Testing16%

The ISTQB Certified Tester Foundation Level (CTFL) is the entry-level credential in the ISTQB Certified Tester scheme. Its purpose is to establish a shared vocabulary and a practical grounding in software testing concepts that hold across delivery approaches - the syllabus is described as relevant to Waterfall, Agile, DevOps and Continuous Delivery. The target audience is broad: testers, test analysts, test engineers, test consultants, test managers, user acceptance testers and software developers, plus adjacent roles such as project managers, quality managers, business analysts and IT directors who need a basic understanding of testing. The published content spans six areas: fundamentals of testing; testing throughout the software development lifecycle; static testing; test techniques; test management; and tool support for testing. Officially, the exam is 40 multiple-choice questions worth 40 points, lasts 60 minutes with 25% extra time for non-native language candidates, and requires 26 points to pass. Note that these figures are published for CTFL v3.1, which the ISTQB site now marks as retired, while CTFL 4.0 is labelled the current Foundation Level certification. Preparation options are accredited training (classroom, virtual or e-learning) or self-study using the syllabus and recommended reading. The credential is also the stated prerequisite for other ISTQB certifications that require Foundation Level.

Common mistakes

When a scenario describes a programmer mistyping a formula and the program later producing a wrong invoice total, the candidate labels the mistyping itself as the 'failure' (or labels the wrong invoice total as the 'defect').

Everyday English treats mistake, bug and failure as synonyms, and exams deliberately describe all three in one scenario so the candidate has to place each event in the right link of the chain.

What to do instead

Memorise the chain error -> defect -> failure and label every scenario by asking 'who/what is at fault and was anything executed?'. A human action is an error; the resulting flaw in a work product is a defect; the observable deviation from expected behaviour during execution is a failure. Practise by rewriting one-sentence bug reports into the three-part chain.

Selecting an answer that says a thoroughly tested system is proven to have no remaining defects, or that exhaustive testing is feasible if testers are given enough time, because the option sounds like the 'safe, thorough' choice.

The distractors are written to reward conscientious-sounding answers, while the seven testing principles require the opposite conclusion (testing shows the presence of defects, exhaustive testing is impossible, testing is context dependent).

What to do instead

Learn the seven principles as short slogans and, for every question, ask which principle is being tested before reading the options. Treat any option containing 'proves', 'guarantees', 'zero defects' or 'test everything' as a flag to re-check.

In a question about reviewing a requirements document against a checklist versus running the built product with real users, the candidate swaps verification and validation labels.

Both words mean 'checking' in ordinary speech, and the exam rarely uses the exact phrasing from the syllabus, instead describing the activity indirectly.

What to do instead

Anchor each term to one question: verification asks 'are we building the product right?' (specifications, reviews, static work, no execution) and validation asks 'are we building the right product?' (user needs, acceptance testing, executable behaviour). Before answering, decide whether the activity compares against a specification or against user needs.

A question describes testing the interactions and interfaces between two finished components, and the candidate answers 'system testing' or 'acceptance testing' instead of component integration testing.

The levels look like a simple ladder of size, so candidates map 'bigger than a component' to the next level up without checking the stated objective of the level.

What to do instead

Build a two-column table for each level (component, component integration, system, system integration, acceptance) listing its objective, typical test basis and typical responsible party. Interface and interaction testing belongs to integration levels, whichever pair of units is involved; end-to-end behaviour against requirements belongs to system testing.

When asked which activities happen in an iterative or incremental lifecycle, the candidate states that regression testing at all levels is mandatory in every iteration, or that in the V-model testing only starts after coding is complete.

Candidates generalise from one model they know, and 'V-model' visually suggests a single late testing phase, while 'iteration' suggests repeating everything fully each time.

What to do instead

Learn each lifecycle by its distinguishing feature rather than its diagram: the V-model pairs each development level with a corresponding test level and requires early test design, while iterative lifecycles allow different test levels to be entered, exited and re-entered per iteration with regression scoped to the risk of change. Answer using the characteristic named in the question stem.

Answering that static testing cannot find defects in requirements or design documents because no code exists to run, or that static analysis is a type of formal review performed by people.

Candidates equate testing with execution, and the word 'analysis' feels like a human judgement activity, so the tool-based and human-based branches get merged.

What to do instead

Hold one dividing line: static testing involves no execution of the software under test and splits into reviews (human) and static analysis (tool-based, typically on code and models). Then check the question stem for 'tool', 'compiler', 'coding standard' versus 'meeting', 'checklist', 'reviewers' to pick the branch.

Mixing up review roles and formality: naming the author as the person who leads a formal inspection, giving the moderator the job of recording findings, or ranking a walkthrough as more formal than a technical review.

The role names are familiar job titles in real workplaces but have precise definitions in the syllabus, and the four review types differ mainly by degree of formality rather than by obvious features.

What to do instead

Memorise formality order (informal review, walkthrough, technical review, inspection) and a one-line role map: manager decides what and when, moderator leads and plans, author fixes, scribe records, reviewers examine. For a question, first identify who is 'leading' (moderator in inspections) and who is 'recording' (scribe).

Given a valid input range, the candidate writes only tests for the boundaries themselves (for example 1 and 100 for the range 1-100) and omits the values immediately either side, then gives a boundary value analysis count that is wrong.

Boundary value analysis is taught with the phrase 'test the boundaries', so candidates stop at the edge values, and the 2-value versus 3-value variants are rarely distinguished in everyday discussion.

What to do instead

Always write out the partition tables first, then derive boundaries, including invalid boundaries: for 1-100 use 0, 1, 100, 101 (2-value) or 0, 1, 2, 99, 100, 101 (3-value). Read the stem to see which variant is implied and state the count explicitly, remembering each boundary belongs to a specific partition.

Computing white-box coverage as the number of passing tests divided by total tests, or claiming 100% statement coverage implies 100% decision coverage.

Percentages are read as 'success rate', and the one-way relationship between decision and statement coverage is counter-intuitive because decision coverage sounds strictly stronger in the wrong direction.

What to do instead

Fix the formula in mind: coverage = exercised items / total items of that type (statements or decisions). Then commit the implication to memory as '100% decision coverage guarantees 100% statement coverage, but not the reverse', because a decision can be exercised without its statements differing in outcome. Re-derive it on a small two-branch example before answering.

In risk-based testing questions the candidate ranks a risk by likelihood alone, or treats product risk and project risk as the same thing, so the chosen test priority and depth are wrong.

Risk is used loosely in everyday speech, and both product and project risks appear in the same syllabus chapter, so candidates assume any risk mentioned is about defects in the software.

What to do instead

Always apply risk level = likelihood x impact, and classify first: product risks concern quality characteristics of the software (a defect may harm users), project risks concern the management of the project (schedule, staffing, suppliers). Then map the top risks to earlier and deeper testing, and state that risk analysis and control are revisited as the project changes.

Choosing an answer that says a test automation or test management tool removes the need for testers' judgement, guarantees better software quality, or that the tool with the lowest licence cost is always the right selection.

Vendor messaging and everyday experience make tools sound like solutions to quality problems, and the syllabus's emphasis on tool support benefits makes the 'more automation is better' option attractive.

What to do instead

Learn the standard caveats: tools support but do not replace human judgement, they carry their own risks (unrealistic expectations, vendor lock-in, effort to maintain scripts, underestimating the learning curve), and tool selection is a structured evaluation of needs, constraints and a pilot, not a price comparison. Reject any option containing 'replaces', 'guarantees' or 'always'.

Exam requirements can change. Confirm current details with the exam provider.

ISTQB Foundation practice

200 questions. Each one lists the choices, the correct answer, and an explanation. With JavaScript, this list opens one question at a time. The checker at the top of this page saves progress in this browser when it is available.

  1. Question 1Fundamentals of Testing

    Which statement best describes software testing according to ISTQB?

    1. A single phase performed only after all coding work has been completed
    2. A set of activities that finds defects and evaluates product quality Correct answer.
    3. A technique for proving that a program contains no remaining defects
    4. The process of removing defects from source code before it is compiled

    Explanation

    Testing is a set of activities concerned with discovering defects and evaluating the quality of work products; it includes both static and dynamic techniques and spans the whole lifecycle. It is neither a single late phase nor a proof of correctness.

  2. Question 2Fundamentals of Testing

    Which of the following is a typical objective of testing?

    1. Causing failures and finding defects in the test object Correct answer.
    2. Removing the root cause of every incident found in production
    3. Demonstrating that no defects remain in the product
    4. Guaranteeing that the software will be reliable in production

    Explanation

    Typical test objectives include causing failures and finding defects, as well as providing information about quality and giving confidence in the test object. Testing reduces risk but can never demonstrate complete absence of defects or give guarantees.

  3. Question 3Fundamentals of Testing

    A developer types the wrong operator into a calculation. Which term describes this human mistake?

    1. A failure, because the user receives an incorrect result
    2. A defect, because the source code contains a fault
    3. An error, because a person made a mistake Correct answer.
    4. A root cause, because it explains the whole incident

    Explanation

    A human action that produces an incorrect result is an error. An error may introduce a defect into a work product, and that defect may cause a failure when the code is executed.

  4. Question 4Fundamentals of Testing

    What is meant by the root cause of a defect?

    1. The test case that exposed the defect during execution
    2. The incident report written after the failure was observed
    3. The fundamental reason why a defect was introduced Correct answer.
    4. The difference between the actual and the expected results

    Explanation

    The root cause is the fundamental reason why a defect was introduced, and identifying it helps prevent similar defects in the future. The failure is the observed deviation from expected behaviour, which is a symptom rather than the cause.

  5. Question 5Fundamentals of Testing

    Which testing principle explains why testing can show that defects are present but can never prove that there are none?

    1. Tests must be reviewed and revised regularly
    2. Testing shows the presence of defects, not their absence Correct answer.
    3. Exhaustive testing is impossible in every project
    4. Defects tend to cluster in a small number of modules

    Explanation

    This principle states that testing reduces the likelihood of undetected defects remaining, but even a test run that finds nothing cannot prove the software is correct. It is the reason testing is described as a risk-reduction activity rather than a proof.

  6. Question 6Fundamentals of Testing

    Repeating the same set of regression tests over many releases gradually stops revealing new defects. Which principle does this illustrate?

    1. Testing is context dependent
    2. The pesticide paradox Correct answer.
    3. Early testing saves time and money
    4. Defect clustering in risky modules

    Explanation

    The pesticide paradox states that if the same tests are repeated over and over, they eventually stop finding new defects. Test cases and test data therefore need to be reviewed and updated regularly to remain effective.

  7. Question 7Fundamentals of Testing

    Which group usually provides the highest level of independence from the author of the code under test?

    1. Testers from an external organisation Correct answer.
    2. The business analyst of the same project
    3. A developer from the same team
    4. The developer who wrote the code

    Explanation

    Independence increases as testers move away from the author: from the author, to peers in the same team, to testers outside the team, and finally to testers outside the organisation. External testers are therefore the most independent, although they may give slower feedback.

  8. Question 8Fundamentals of Testing

    Checking that a work product meets the requirements specified for it is an example of which activity?

    1. Verification, because it checks conformance to requirements Correct answer.
    2. Validation, because it checks that the user's needs are satisfied
    3. Confirmation testing, because it re-tests a corrected defect
    4. Regression testing, because it re-executes earlier test cases

    Explanation

    Verification checks that work products conform to the requirements specified for them, often described as building the product right. Validation instead checks that the product fulfils the intended use and user needs.

  9. Question 9Fundamentals of Testing

    A project team finds that 60% of all defects come from two of its thirty modules. Which principle should guide where to focus test effort?

    1. Exhaustive testing is impossible for large systems
    2. Defect clustering, so effort should follow risk Correct answer.
    3. The pesticide paradox requires new test cases
    4. Testing should start early in the lifecycle

    Explanation

    The defect clustering principle states that a small number of modules usually contain most of the defects. Test effort should therefore be prioritised according to risk and defect concentration rather than spread evenly.

  10. Question 10Fundamentals of Testing

    A team plans to test every possible combination of inputs for a simple form. Which principle tells them this plan is unrealistic and that risk-based prioritisation should be used instead?

    1. Exhaustive testing is impossible Correct answer.
    2. Absence of errors is a fallacy
    3. Testing is context dependent
    4. Defects cluster together in a few components

    Explanation

    Exhaustive testing of all input and precondition combinations is impossible except in trivial cases. Risk analysis, prioritisation and coverage-based techniques must therefore be used to select a feasible set of tests.

  11. Question 11Fundamentals of Testing

    Which test process activity identifies and prioritises test conditions based on the test basis?

    1. Test monitoring, which tracks progress against the plan
    2. Test analysis, which determines what should be tested Correct answer.
    3. Test design, which specifies how the conditions will be covered
    4. Test execution, which compares actual and expected results

    Explanation

    Test analysis analyses the test basis to identify test conditions, answering the question of what should be tested, and prioritises them. Test design follows and determines how those conditions will be covered by test cases and test data.

  12. Question 12Fundamentals of Testing

    Which of the following is a typical work product of the test design activity?

    1. An incident report describing unexpected behaviour
    2. A test completion report summarising results
    3. A test plan describing the schedule and resources
    4. Test cases and sets of expected results Correct answer.

    Explanation

    Test design produces test cases, sets of expected results, test data requirements and, where relevant, test charters and coverage items. These form part of the testware that supports later execution and reporting.

  13. Question 13Fundamentals of Testing

    Which test level focuses on interactions and interfaces between components of a system?

    1. Acceptance testing by business users
    2. System testing against end-to-end requirements
    3. Component testing of individual units
    4. Integration testing Correct answer.

    Explanation

    Integration testing focuses on interactions and interfaces between components or systems, which is where defects in communication and data exchange tend to appear. Component testing, by contrast, tests components in isolation.

  14. Question 14Fundamentals of Testing

    Business users run realistic tasks on a completed system to decide whether it should be released for use. Which type of acceptance testing does this describe?

    1. Contractual acceptance testing against a contract
    2. User acceptance testing Correct answer.
    3. Regulatory acceptance testing of legal requirements
    4. Operational acceptance testing of backup and recovery

    Explanation

    User acceptance testing is performed by the intended users in a realistic environment to confirm that the system supports their business needs and is acceptable for release. The other acceptance types address operational, contractual and regulatory concerns.

  15. Question 15Fundamentals of Testing

    After a defect is fixed, which type of testing checks that the fix has actually resolved the problem?

    1. Regression testing that re-runs existing test cases
    2. Non-functional testing of performance
    3. Smoke testing of the main build functionality
    4. Confirmation testing of the corrected defect Correct answer.

    Explanation

    Confirmation testing, also called re-testing, executes the test that originally failed to check that the specific defect has been resolved. Regression testing is then used to check that the change has not broken other parts of the system.

  16. Question 16Fundamentals of Testing

    Which test type derives test conditions from the internal structure of the test object?

    1. White-box testing of the code structure Correct answer.
    2. Functional testing based on specified behaviour
    3. Non-functional testing of quality characteristics
    4. Change-related testing of modifications

    Explanation

    White-box testing derives test conditions from the internal structure, such as code, architecture, design or data flow. Black-box testing, by contrast, derives them from specifications and other external descriptions of behaviour.

  17. Question 17Fundamentals of Testing

    A team measures the response time and CPU usage of a new web application during load. Which test type are they performing?

    1. Component integration testing
    2. Functional testing
    3. Non-functional testing Correct answer.
    4. Regression testing

    Explanation

    Response time and CPU usage are quality characteristics, so measuring them is non-functional testing. Non-functional testing evaluates how well the system behaves rather than whether it implements the required functions correctly.

  18. Question 18Fundamentals of Testing

    What does the shift-left approach recommend?

    1. Reducing the number of test levels in a project
    2. Replacing all manual testing with automated scripts
    3. Moving test execution to a dedicated team after release
    4. Starting testing activities earlier in the lifecycle Correct answer.

    Explanation

    Shift left means performing testing activities earlier, for example reviewing requirements and designing tests before code exists, so that defects are found when they are cheaper to fix. It complements later testing rather than replacing it.

  19. Question 19Fundamentals of Testing

    Which statement about the V-model is correct?

    1. It requires all testing to be automated within a continuous pipeline
    2. It pairs each development phase with a corresponding test level Correct answer.
    3. It treats testing as a single phase performed after system design
    4. It allows each test level to be executed before the corresponding development phase

    Explanation

    In the V-model each development phase, such as requirements or design, corresponds to a test level, and test planning for a level starts in parallel with the matching development phase. The tests themselves are executed after the corresponding development work is complete.

  20. Question 20Fundamentals of Testing

    Which practice is most characteristic of an agile approach to testing?

    1. Handing testing over to a separate independent department
    2. Executing system tests only after all coding has finished
    3. Preparing a detailed test plan once, at the start of the project
    4. Testing continuously within each iteration by the whole team Correct answer.

    Explanation

    Agile approaches favour continuous testing within each iteration, with the whole team involved and fast feedback from developers, testers and business representatives. Documentation and planning are kept lean and are revisited as understanding grows.

  21. Question 21Fundamentals of Testing

    What is the main benefit of establishing traceability between the test basis and the testware?

    1. It eliminates the need for regression testing after a change
    2. It supports impact analysis and coverage measurement Correct answer.
    3. It removes the need to review test cases before execution
    4. It guarantees that no defects will escape to production

    Explanation

    Traceability links testware to the requirements and other sources it was derived from, which allows coverage to be measured and supports impact analysis when requirements change. It also helps report on the status of testing and on the coverage of risks.

  22. Question 22Fundamentals of Testing

    A team finds and fixes every defect reported in testing, yet users still find the system unusable for their work. Which principle does this illustrate?

    1. The pesticide paradox
    2. Defect clustering
    3. Exhaustive testing is impossible
    4. The absence-of-errors fallacy Correct answer.

    Explanation

    The absence-of-errors fallacy states that finding and fixing defects does not help if the system does not fulfil users' needs and expectations. Validation against the intended use is therefore essential alongside defect removal.

  23. Question 23Fundamentals of Testing

    A safety-critical medical device and a public marketing website are tested with very different levels of rigour, documentation and formality. Which testing principle does this reflect?

    1. Testing shows the presence of defects, not their absence
    2. Defects cluster in a small number of modules
    3. Early testing saves time and money
    4. Testing is context dependent Correct answer.

    Explanation

    Testing is context dependent: the approach, degree of rigour and level of documentation must match the domain, the risks and any regulatory requirements of the product. A medical device and a marketing site therefore warrant very different testing.

  24. Question 24Fundamentals of Testing

    Why does a DevOps approach typically improve the feedback that testers receive?

    1. It schedules testing as a single phase before deployment
    2. It automates build, test and deployment in pipelines Correct answer.
    3. It shifts all testing responsibility to operations engineers
    4. It removes the need for any manual testing before release

    Explanation

    DevOps relies on automated build, test and deployment pipelines with continuous integration and delivery. This gives rapid feedback on every change and lets the team correct problems quickly, while testing remains a whole-team responsibility.

  25. Question 25Fundamentals of Testing

    Which set of activities belongs primarily to the test manager role rather than the tester role?

    1. Analysing the test basis and designing test cases
    2. Planning, monitoring and controlling test activities Correct answer.
    3. Executing tests and reporting incidents
    4. Evaluating work products through technical reviews

    Explanation

    The test manager is accountable for planning, monitoring, controlling and completing test activities, including resources, schedules and reporting. Testers concentrate on the technical work of analysis, design, execution and evaluation.

  26. Question 26Fundamentals of Testing

    During a code review, a developer's statement is found to use 'less than' where 'less than or equal to' was intended. The incorrect statement in the code is best described as which of the following?

    1. A test condition
    2. A failure
    3. A defect Correct answer.
    4. An error

    Explanation

    In testing terminology the human mistake is the error, the flawed item left in a work product is the defect (fault), and the observable deviation in behaviour when that defect is executed is the failure. The incorrect statement sitting in the code is therefore a defect. Failures appear only when the defect is executed under the right conditions.

  27. Question 27Fundamentals of Testing

    Which statement best distinguishes testing from debugging?

    1. Testing is static; debugging is dynamic
    2. Both terms describe the same activity performed by different roles
    3. Testing proves correctness; debugging proves incorrectness
    4. Testing finds failures; debugging finds and fixes their causes Correct answer.

    Explanation

    Testing is a structured activity that reveals failures and provides information about quality, whereas debugging is the development activity that locates the cause of a failure, fixes it and checks the fix. The two are complementary but have different objectives and often different owners. Neither activity can prove that software is correct.

  28. Question 28Fundamentals of Testing

    Which of the following is a recognised test objective?

    1. Gaining confidence in the quality of the test object Correct answer.
    2. Showing that the developers made no mistakes
    3. Replacing acceptance testing with automated checks
    4. Proving that the software contains no defects whatsoever

    Explanation

    Typical test objectives include finding defects, evaluating work products, providing information to decision makers and gaining confidence in the quality of the test object. Testing can never demonstrate the complete absence of defects, and it is not a means of assigning blame. Automation supports testing but does not remove the need for acceptance testing.

  29. Question 29Fundamentals of Testing

    A tester reads the requirements specification and lists the individual features and conditions that need to be covered, but has not yet decided how to test them. Which test process activity is being carried out?

    1. Test analysis Correct answer.
    2. Test execution
    3. Test design
    4. Test implementation

    Explanation

    Test analysis uses the test basis to identify and prioritise test conditions, that is, what is to be tested, without yet deciding how. Test design then elaborates those conditions into test cases and other testware. Implementation organises and prioritises the testware and execution runs it.

  30. Question 30Fundamentals of Testing

    A project schedules reviews of the requirements and design documents in its first two weeks, before any code is written. Which testing principle does this best illustrate?

    1. Defects cluster together in a few modules
    2. Early testing saves time and money Correct answer.
    3. Repeating the same tests stops finding new defects
    4. Exhaustive testing is impossible

    Explanation

    The principle of early testing states that testing activities should start as early as possible in the lifecycle, including static testing of documents. Defects found in requirements or design are far cheaper to correct than the same defects found later. The other options concern coverage limits, defect distribution and the pesticide paradox.

  31. Question 31Fundamentals of Testing

    A tester designs test cases using only the requirements specification and the user interface, without examining the source code. Which term best describes this approach?

    1. Black-box testing Correct answer.
    2. Structural testing
    3. White-box testing
    4. Static analysis

    Explanation

    Black-box (specification-based) testing derives test conditions from documented requirements and observable behaviour, without reference to the internal structure of the test object. White-box and structural testing instead use the internal structure. Static analysis examines code or documents without executing them, which is not what is described.

  32. Question 32Fundamentals of Testing

    Which of the following is the best example of an exit criterion for a test level?

    1. Test cases have been designed by two testers
    2. No critical defects remain open Correct answer.
    3. The test plan has been approved by the project manager
    4. The test environment has been booked for four weeks

    Explanation

    Exit criteria define what must be achieved for a test level or activity to be considered complete, such as defect resolution levels, coverage thresholds or test case pass rates. Having no open critical defects is a measurable completion condition. Booking an environment, designing cases and approving a plan are preconditions or progress states rather than completion criteria.

  33. Question 33Fundamentals of Testing

    A payroll system has been in production for six years. The tax calculation module is modified for new legislation. In addition to testing the change itself, what should maintenance testing include?

    1. Only a re-run of the acceptance tests performed before the first release
    2. Only testing of the new tax rules, since the rest of the system is unchanged
    3. Regression testing of unchanged areas guided by impact analysis Correct answer.
    4. Testing of the user interface only, because the change is internal

    Explanation

    Maintenance testing covers both the changes made and the parts that could be affected by them, which are identified through impact analysis. Because changed code can break untouched functionality, regression testing of unchanged areas is essential. The scope is therefore wider than the change itself and wider than the original acceptance tests.

  34. Question 34Fundamentals of Testing

    During test execution, a test manager sees that most planned test cases have been run, but a quarter of them are blocked by an unstable test environment and the defect detection rate has dropped sharply. What is the most appropriate control action?

    1. Declare the exit criteria met because the majority of the planned test cases have already been executed
    2. Add extra test cases to raise coverage before the release date
    3. Escalate the environment issue and re-plan the remaining execution Correct answer.
    4. Stop all testing until the next planned release

    Explanation

    Test monitoring compares actual progress with the plan, and test control takes corrective action when deviations are found. Blocked tests mean the reported execution count overstates real coverage, so the environment problem must be resolved and the remaining work re-planned. Declaring completion or adding more cases would not address the blockage.

  35. Question 35Testing Throughout the Software Development Lifecycle

    Which statement describes a characteristic of the waterfall model?

    1. A phase begins only after the previous phase is complete Correct answer.
    2. Working software is delivered in short, repeated iterations
    3. Acceptance tests are written before any code is produced
    4. Testing is carried out continuously, in every phase

    Explanation

    In a sequential (waterfall) lifecycle the phases are carried out one after another, and a phase is entered only when the objectives of the preceding phase have been met, with testing usually treated as a distinct phase after coding. Incremental delivery, early test writing and continuous testing are features of iterative or agile lifecycles.

  36. Question 36Testing Throughout the Software Development Lifecycle

    What is the defining feature of the V-model?

    1. Test execution begins as soon as the first lines of code are written
    2. Each development phase has a corresponding test level planned alongside it Correct answer.
    3. Each increment is fully tested before the next increment starts
    4. Testing is performed by an independent team once the whole system is built

    Explanation

    The V-model keeps the sequential phases but pairs each development phase with the test level that verifies its output, for example requirements with system testing and detailed design with component testing, so test planning starts early. Incremental delivery and immediate test execution belong to other lifecycle models.

  37. Question 37Testing Throughout the Software Development Lifecycle

    Which of the following is an example of validation?

    1. Running static analysis tools over the source code to find coding defects
    2. Reviewing the requirements specification for consistency and completeness
    3. Checking that the code conforms to the agreed coding standards and naming rules
    4. Having end users confirm that the system supports their business processes Correct answer.

    Explanation

    Validation asks whether the product meets the users' needs and expectations, and is typically demonstrated through acceptance testing with real users. Reviews, coding standard checks and static analysis are verification activities that compare work products against their specified requirements.

  38. Question 38Testing Throughout the Software Development Lifecycle

    Which type of testing is performed after a defect is fixed to establish that the fix has resolved the reported problem?

    1. Confirmation testing Correct answer.
    2. Maintainability testing
    3. Regression testing
    4. Operational acceptance testing

    Explanation

    Confirmation testing, also called re-testing, checks that a specific defect has been fixed and that the previously failing test now passes. Regression testing is broader and searches for unintended side effects of the change elsewhere in the system.

  39. Question 39Testing Throughout the Software Development Lifecycle

    At which test level are the interfaces and interactions between components or systems the main focus?

    1. Component testing
    2. Integration testing Correct answer.
    3. Acceptance testing
    4. System testing

    Explanation

    Integration testing focuses on the interfaces and interactions between components or between separate systems. Component testing examines single components in isolation, while system and acceptance testing take the complete product as the object of testing.

  40. Question 40Testing Throughout the Software Development Lifecycle

    Operational acceptance testing is mainly concerned with which aspect of a system?

    1. Verifying that each of the defined business processes is fully supported by the system
    2. Confirming that the system can be run and maintained in its production environment Correct answer.
    3. Obtaining sign-off against a contractually agreed specification
    4. Checking that the system complies with a government regulation

    Explanation

    Operational acceptance testing is carried out by operations staff or administrators to confirm that the system can be operated, backed up, recovered and maintained in production. Business process support, contractual sign-off and legal compliance belong to user, contractual and regulatory acceptance testing.

  41. Question 41Testing Throughout the Software Development Lifecycle

    End-to-end behaviour and the non-functional characteristics of a complete system are typically evaluated at which test level?

    1. System testing Correct answer.
    2. Integration testing
    3. Component testing
    4. Acceptance testing

    Explanation

    System testing evaluates the behaviour of the whole system end to end, including non-functional characteristics such as performance and reliability, usually against the requirements specification. Component and integration testing deal with parts of the system rather than the complete product.

  42. Question 42Testing Throughout the Software Development Lifecycle

    In an incremental development model, what is normally produced at the end of each increment?

    1. A working part of the product that can be demonstrated and evaluated Correct answer.
    2. A complete and formally approved specification of all the requirements
    3. A set of architectural design documents for later coding
    4. A fully tested product that is ready for release

    Explanation

    Incremental development builds the product in portions, and each increment produces a working part that can be demonstrated, tested and sometimes delivered to users. Complete specifications and design documents are produced up front in sequential lifecycles, and a release-ready product is the result of the final increment only.

  43. Question 43Testing Throughout the Software Development Lifecycle

    What does applying the 'shift left' principle mainly involve?

    1. Transferring responsibility for all testing to business users
    2. Performing testing activities earlier in the software lifecycle Correct answer.
    3. Moving the test team physically closer to the development team
    4. Postponing test execution until the design has been fully completed and approved

    Explanation

    Shifting left means carrying out testing activities such as reviews, static analysis and test design as early as possible, instead of waiting for a test phase at the end of the project. Early testing reduces the cost of fixing defects and supports prevention rather than detection.

  44. Question 44Testing Throughout the Software Development Lifecycle

    In test-driven development, what is the first activity for each new piece of functionality?

    1. Run the full regression suite to establish a baseline before coding
    2. Refactor the production code to remove any duplication that has been introduced
    3. Write the production code first and afterwards write tests that cover it
    4. Write a test that fails because the functionality does not exist yet Correct answer.

    Explanation

    TDD follows a repeated cycle: write a test that fails, write just enough code to make it pass, then refactor the code while keeping all tests passing. Production code is therefore never written before a failing test exists.

  45. Question 45Testing Throughout the Software Development Lifecycle

    In behaviour-driven development, in which form are acceptance criteria usually expressed?

    1. As a set of code coverage targets agreed with the developers
    2. As Given/When/Then scenarios written in business-readable language Correct answer.
    3. As a list of entry and exit criteria for each test level
    4. As a decision table listing every combination of input values and expected outputs

    Explanation

    BDD expresses acceptance criteria as scenarios using Given (the context), When (the action) and Then (the expected outcome), phrased so that business stakeholders can read and confirm them. Decision tables are a black-box design technique and coverage targets are a measure rather than a way of expressing criteria.

  46. Question 46Testing Throughout the Software Development Lifecycle

    Which of the following is a typical entry criterion for starting system testing?

    1. The required level of statement coverage has been achieved
    2. The residual risk is low enough for the product to be released
    3. All defects found at earlier test levels have been closed
    4. The test environment and the required test data are available Correct answer.

    Explanation

    Entry criteria state what must be in place before a test level can begin, such as available testware, a ready test environment and test data, and predecessor defects that have been resolved. Closing all defects, achieving coverage targets and accepting residual risk relate to exit criteria or to release decisions.

  47. Question 47Testing Throughout the Software Development Lifecycle

    Which statement about regression testing in an iterative project is correct?

    1. The suite tends to grow with each increment and is normally run with automated tools Correct answer.
    2. It is performed only when the requirements have changed in a new increment
    3. It is only needed once, before the product is released to customers
    4. It is replaced by confirmation testing once the first increment is complete

    Explanation

    Every new increment can disturb functionality that already worked, so regression tests are added and re-run frequently, which is only practical with a growing, automated suite. Regression testing is a continuous activity and cannot be replaced by confirmation testing, which only checks that a fix worked.

  48. Question 48Testing Throughout the Software Development Lifecycle

    Which statement best describes testing in an agile development approach?

    1. Testing is carried out only by an independent team at the end of the project
    2. Testing follows a documented test plan that is fixed at the start of the project
    3. Testing is integrated into every iteration rather than confined to a separate phase Correct answer.
    4. Testing is limited to automated unit tests written by the developers

    Explanation

    In agile development testing is continuous and embedded in each iteration, with testers working alongside developers and business representatives. A fixed up-front plan and testing restricted to an independent team at project end belong to sequential lifecycles.

  49. Question 49Testing Throughout the Software Development Lifecycle

    In the V-model, which work product does system testing primarily verify?

    1. The code coverage achieved by the component tests
    2. The architecture and interfaces between the subsystems
    3. The specified functional and non-functional requirements Correct answer.
    4. The detailed design of the individual components

    Explanation

    In the V-model each test level is paired with the development phase whose output it checks: the requirements specification is verified by system testing, the architecture by integration testing and the detailed design by component testing. Coverage figures are measurements, not a work product to be verified.

  50. Question 50Testing Throughout the Software Development Lifecycle

    Which of the following is normally the test basis for component testing?

    1. The detailed design and the component's specifications Correct answer.
    2. The acceptance criteria agreed with the customer
    3. The user requirements specification and business process models
    4. The system architecture and interface specifications

    Explanation

    Component testing is based on the detailed design and component specifications and is usually performed by the developers who wrote the code. Requirements and business process models underpin system and acceptance testing, while architecture and interfaces are the basis for integration testing.

  51. Question 51Testing Throughout the Software Development Lifecycle

    When a bottom-up strategy is used for integration testing, what must be built to allow the lower-level components to be tested?

    1. Stubs that simulate the components not yet built
    2. A production copy of the database and its data
    3. Drivers that call the components under test Correct answer.
    4. A test harness containing only the user interface

    Explanation

    Bottom-up integration starts with the lowest-level components, so drivers are needed to call them and supply the control that the not-yet-integrated upper layers would normally provide. Stubs, which replace components that are called, are used in top-down integration.

  52. Question 52Testing Throughout the Software Development Lifecycle

    Which of the following statements about system testing is correct?

    1. It is usually performed by an independent test team using the requirements as a basis Correct answer.
    2. It is performed on interfaces between units before integration begins
    3. It is performed by developers on individual functions and classes
    4. It is performed by customers to decide whether to accept the system

    Explanation

    System testing evaluates the complete system against its functional and non-functional requirements and is typically carried out by an independent test team. Developers test individual components, customers perform acceptance testing, and interface testing belongs to integration testing.

  53. Question 53Testing Throughout the Software Development Lifecycle

    How does a DevOps approach typically change testing?

    1. It makes testing the sole responsibility of the operations team
    2. It removes the need for regression testing by releasing more frequently
    3. It relies on automated pipelines that run tests for every change delivered Correct answer.
    4. It moves all testing into a separate phase after deployment to production

    Explanation

    DevOps builds an automated delivery pipeline in which tests run against every change, supporting continuous integration and continuous delivery and giving fast feedback. Frequent releases increase rather than remove the need for regression testing, and testing remains a shared activity rather than an operations-only task.

  54. Question 54Testing Throughout the Software Development Lifecycle

    Which of the following is true of maintenance testing?

    1. It is limited to testing the code that was changed
    2. It covers the changed part and the possible impact on the rest of the system Correct answer.
    3. It is only performed when a new system is first installed
    4. It is not needed when the change is limited to configuration data

    Explanation

    Maintenance testing covers both the modified part of the system and, through regression testing, the parts that may have been affected by the change. It applies to any change to a live system, including data and configuration changes and migrations.

  55. Question 55Testing Throughout the Software Development Lifecycle

    Which statement correctly distinguishes test levels from test types?

    1. Test levels and test types are alternative names for the same grouping of activities
    2. Test levels relate to development stages; test types relate to the purpose of testing Correct answer.
    3. Test levels describe the nature of the tests, while test types describe the phases of development
    4. Test levels apply only to agile projects, while test types apply only to sequential ones

    Explanation

    Test levels such as component, integration, system and acceptance group activities around stages of development, while test types such as functional, non-functional, white-box and change-related describe the purpose of the testing. The same test type can be applied at more than one test level.

  56. Question 56Testing Throughout the Software Development Lifecycle

    A medical device manufacturer must show that its product meets a national safety standard before it may be sold. Which type of acceptance testing does this describe?

    1. Operational acceptance testing
    2. Regulatory acceptance testing Correct answer.
    3. User acceptance testing
    4. Contractual acceptance testing

    Explanation

    Regulatory acceptance testing is required when a system must comply with laws, regulations or safety standards before release, and is often mandated or witnessed by a regulator. Operational, contractual and user acceptance testing address run-time supportability, contract compliance and business fitness respectively.

  57. Question 57Testing Throughout the Software Development Lifecycle

    The extent of maintenance testing after a change depends on which pair of factors?

    1. The number of defects found in the previous release and the project budget
    2. The programming language used and the number of automated tests
    3. The risk of the change and the size of both the change and the system Correct answer.
    4. The number of testers available and the length of the release cycle

    Explanation

    The scope of maintenance testing is driven by the degree of risk attached to the change and by the size of the change and of the existing system, which together determine how much regression testing is warranted. Resourcing, technology and budget factors are not the factors identified for this decision.

  58. Question 58Testing Throughout the Software Development Lifecycle

    Which statement best distinguishes acceptance test-driven development from test-driven development?

    1. ATDD is driven by business acceptance criteria; TDD is a coding design technique Correct answer.
    2. ATDD covers only non-functional requirements, whereas TDD covers functional requirements and unit design
    3. ATDD writes the tests after the code is complete, whereas TDD writes the tests before any code exists
    4. ATDD is performed only by testers, whereas TDD is performed only by business analysts, who own the requirements

    Explanation

    ATDD derives tests from acceptance criteria agreed with business stakeholders before implementation, so development is guided by customer expectations. TDD is a developer-level design technique in which unit tests drive the code and is independent of acceptance criteria.

  59. Question 59Testing Throughout the Software Development Lifecycle

    Why is tester involvement in requirements reviews valuable in any lifecycle model?

    1. It prevents defects and builds a basis for designing tests early Correct answer.
    2. It guarantees that no requirements defects will reach the design phase
    3. It allows the test team to approve the requirement's business value
    4. It replaces the need for acceptance testing later in the project

    Explanation

    Involving testers in requirements reviews applies the principle of early testing: defects are found while they are cheap to correct, and the requirements become a basis for designing system and acceptance tests before code exists. Reviews reduce but cannot eliminate defects, and they do not substitute for later testing.

  60. Question 60Testing Throughout the Software Development Lifecycle

    Which test level focuses primarily on the interfaces and interactions between components or between systems?

    1. Integration testing Correct answer.
    2. Component testing
    3. Acceptance testing
    4. System testing

    Explanation

    Integration testing concentrates on the interfaces and interactions between components or between systems, so defects in the communication between parts are exposed. Component testing deals with a single component in isolation, while system testing and acceptance testing examine a complete system rather than the links between its parts.

  61. Question 61Testing Throughout the Software Development Lifecycle

    Which statement best describes verification?

    1. It checks whether the delivered system satisfies the users' business needs.
    2. It checks whether work products conform to their specified requirements. Correct answer.
    3. It is another name for acceptance testing.
    4. It can only be carried out by executing the software under test.

    Explanation

    Verification answers the question 'are we building the product right?' by comparing work products such as requirements, designs, code and tests against their specified requirements. It can be static, for example through reviews, or dynamic through execution, so it is not restricted to running the software.

  62. Question 62Testing Throughout the Software Development Lifecycle

    Who is normally responsible for carrying out acceptance testing?

    1. An independent test team from IT.
    2. The intended users and customers, supported by testers. Correct answer.
    3. The developers who wrote the code under test.
    4. The team that maintains the automated test suite.

    Explanation

    Acceptance testing is validation-oriented and depends on knowledge of business needs, so the intended users and customers own it, often supported by testers who help design and run the tests. Developers and IT test teams may prepare the environment or provide data, but they do not decide acceptance.

  63. Question 63Testing Throughout the Software Development Lifecycle

    A team's automated suite is dominated by end-to-end UI tests and contains very few component tests. What is the most likely consequence?

    1. Defects are detected earlier in the lifecycle.
    2. Feedback is slow and the suite costs more to maintain. Correct answer.
    3. Component-level defects stop reaching the code base.
    4. Business-process coverage becomes impossible to achieve.

    Explanation

    The test pyramid principle suggests many fast, fine-grained tests at the lower levels and only a few broad tests at the UI level. A UI-heavy suite runs slowly, is fragile against interface changes and requires much more maintenance effort for the same coverage.

  64. Question 64Testing Throughout the Software Development Lifecycle

    After a defect has been fixed, what is the purpose of confirmation testing?

    1. To measure the performance of the changed component.
    2. To check that no other parts of the system were affected by the fix.
    3. To confirm that the change was reviewed by a colleague.
    4. To check that the specific defect is no longer present. Correct answer.

    Explanation

    Confirmation testing, also called re-testing, verifies that the change made to fix a reported defect actually resolves that defect. Checking whether the change broke anything else is the separate purpose of regression testing, which is usually performed alongside it.

  65. Question 65Testing Throughout the Software Development Lifecycle

    Why should the test environment used for system and acceptance testing resemble the production environment as closely as possible?

    1. Because tests cannot be executed in an environment that differs from production.
    2. To increase confidence that the system will behave as expected in operation. Correct answer.
    3. Because it removes the need for regression testing after release.
    4. Because it makes test data preparation unnecessary.

    Explanation

    Environment differences such as hardware, network configuration or software versions can produce behaviour that never occurs in production, or hide behaviour that does. A realistic environment therefore raises confidence that results obtained during testing will hold in operation and reduces the risk of environment-specific failures after release.

  66. Question 66Testing Throughout the Software Development Lifecycle

    In the agile testing quadrants, tests such as performance and security testing belong to which quadrant?

    1. Q1: technology-facing tests that support the team
    2. Q4: technology-facing tests that critique the product Correct answer.
    3. Q3: business-facing tests that critique the product
    4. Q2: business-facing tests that support the team

    Explanation

    The fourth quadrant contains technology-facing tests that critique the product, which covers non-functional characteristics such as performance, load, reliability and security. The first quadrant holds unit and component tests, the second functional story-level tests, and the third business-facing tests such as exploratory, usability and user acceptance testing.

  67. Question 67Testing Throughout the Software Development Lifecycle

    A contract requires a complete, formally approved specification, and the requirements are stable and well understood. Which lifecycle model fits this situation best?

    1. A sequential (waterfall) model Correct answer.
    2. Test-driven development
    3. An iterative and incremental model
    4. Continuous integration with frequent releases

    Explanation

    Sequential models suit projects where requirements are stable, well documented and unlikely to change, because each phase is completed and baselined before the next begins. Iterative, agile and continuous approaches are chosen when requirements are expected to evolve and early feedback is more valuable than a frozen specification.

  68. Question 68Testing Throughout the Software Development Lifecycle

    Why do the number and names of test levels differ between organizations and lifecycle models?

    1. Because levels are defined to suit the project's context, such as its size, model and risks. Correct answer.
    2. Because test levels replace test types once a lifecycle model has been selected.
    3. Because each test level must be owned by a separate, independent team.
    4. Because standards bodies mandate a different set of levels for each industry.

    Explanation

    Test levels are not fixed by any universal standard; they are defined so that testing at each stage matches the project context, including the lifecycle model, the size and complexity of the system, and the risks being addressed. This is why one project may combine component, integration and system testing while another uses different groupings and names.

  69. Question 69Static Testing

    What does static testing examine?

    1. Test output compared with expected results
    2. The software, under peak load
    3. Work products, without executing them Correct answer.
    4. A running build, using test data

    Explanation

    Static testing examines work products such as requirements, designs, code and test cases by human or tool-based analysis, without executing them. Anything that requires running the software belongs to dynamic testing.

  70. Question 70Static Testing

    Which of the following is a work product that static testing can examine?

    1. The response time recorded during a load test
    2. The memory consumed while a test runs
    3. A requirements specification document Correct answer.
    4. The behaviour observed in an exploratory session

    Explanation

    Static testing applies to work products - documents, models, source code, test cases and the like. Measurements and observations taken while the software runs are results of dynamic testing.

  71. Question 71Static Testing

    Static analysis tools are typically used to detect which kind of problem?

    1. Violations of coding standards Correct answer.
    2. Slow response under peak load
    3. Mismatches between actual and expected output
    4. Incorrect expected results in test cases

    Explanation

    Static analysis is tool-based examination of code (and sometimes other models) without execution, so it is well suited to checking coding standards, unused variables, unreachable code and suspicious data flow. Runtime mismatches and performance behaviour are outside its reach.

  72. Question 72Static Testing

    Which of the following is a review type?

    1. Coverage review
    2. Informal review Correct answer.
    3. Regression review
    4. Boundary review

    Explanation

    The recognised review types are informal review, walkthrough, technical review and inspection. The other names are not review types at all.

  73. Question 73Static Testing

    In a formal review, who ensures that the review process is followed and the meeting stays effective?

    1. The review manager
    2. The moderator Correct answer.
    3. The scribe
    4. The author

    Explanation

    The moderator leads the review meeting, keeps it on track and ensures the agreed process is followed. The author owns the work product and the scribe records the findings.

  74. Question 74Static Testing

    Why is finding defects by static testing usually cheaper than finding them in dynamic testing?

    1. Because static testing needs no reviewers
    2. Because static testing covers all performance risks
    3. Because static testing replaces regression testing
    4. Because defects are found before code is written Correct answer.

    Explanation

    Static testing can be applied to requirements, designs and code as soon as they exist, so defects are corrected before they propagate into later work products and test cycles. The cost of rework grows the later a defect is found.

  75. Question 75Static Testing

    Which defect is most likely to be found by reviewing a requirements specification?

    1. A requirement that contradicts another Correct answer.
    2. A query that runs too slowly on the database
    3. A loop that never terminates
    4. A variable read before it is initialized

    Explanation

    Reviews of requirements look for ambiguity, incompleteness, inconsistency and untestability in the statements themselves, such as two requirements that cannot both hold. The other options are code or runtime issues.

  76. Question 76Static Testing

    What is the main responsibility of the scribe in a review?

    1. Recording the findings and decisions Correct answer.
    2. Correcting the defects that are found
    3. Explaining the work product to the reviewers
    4. Deciding which reviewers should attend

    Explanation

    The scribe captures what the review team finds and decides, producing the record of the review. Selecting participants belongs to planning, and correcting defects is done by the author after the review.

  77. Question 77Static Testing

    Which defect can static testing find but dynamic testing typically cannot?

    1. A crash caused by a null pointer dereference
    2. A memory leak after a long test run
    3. A calculation that returns a wrong result
    4. Code that is never reached in execution Correct answer.

    Explanation

    Unreachable or dead code is invisible to dynamic testing precisely because it never executes, yet a reviewer or static analysis tool can spot it. The other defects only manifest while the software runs.

  78. Question 78Static Testing

    Which activity of the review process is carried out first?

    1. Planning Correct answer.
    2. Individual review
    3. Communication and analysis
    4. Fixing and reporting

    Explanation

    The review process starts with planning, where scope, purpose, roles, techniques, and entry and exit criteria are agreed. Only then can the review be initiated and individual review begin.

  79. Question 79Static Testing

    Which review activity confirms that participants can access the work product and are ready to begin?

    1. Planning
    2. Individual review
    3. Review initiation Correct answer.
    4. Fixing and reporting

    Explanation

    Review initiation ensures the review object is available to the participants, entry criteria are checked and everyone is prepared so the review can meet its objectives. Planning has already fixed scope, roles and criteria.

  80. Question 80Static Testing

    What is the purpose of the individual review activity?

    1. To study the product and note potential defects Correct answer.
    2. To correct the defects that were logged
    3. To record the minutes of the review meeting
    4. To decide whether the exit criteria have been met

    Explanation

    In individual review each reviewer examines the work product on their own, applying the chosen technique, and records potential defects and questions. Consolidating and discussing these findings is a separate activity.

  81. Question 81Static Testing

    Which characteristic is typical of a formal inspection?

    1. The author leads the group to share knowledge
    2. Defined roles, a documented process and metrics Correct answer.
    3. Only managers take part and approve the result
    4. No records are kept of the findings

    Explanation

    An inspection is the most formal review type: it follows a defined process, uses defined roles such as moderator and scribe, and collects metrics so the review process itself can be improved. Author-led knowledge sharing describes a walkthrough.

  82. Question 82Static Testing

    In which review type does the author lead the participants through the work product to explain it?

    1. Technical review
    2. Inspection
    3. Management review
    4. Walkthrough Correct answer.

    Explanation

    A walkthrough is driven by the author, who guides the participants through the work product, often to achieve common understanding and gather feedback. The other types are led differently or have a different purpose.

  83. Question 83Static Testing

    Which statement describes a technical review?

    1. It is a documented peer review by technically qualified reviewers. Correct answer.
    2. It is a meeting where managers approve the project budget.
    3. It is led by the author to explain the document to non-technical staff.
    4. It is an undocumented meeting without defined roles.

    Explanation

    A technical review is a peer review carried out by technically qualified reviewers using a documented process, with the aim of reaching consensus on the technical content of the work product. It is more formal than a walkthrough but less formal than an inspection.

  84. Question 84Static Testing

    Which factor contributes most to the success of reviews?

    1. Focusing only on defects and never on improvements
    2. Adequate preparation and management support Correct answer.
    3. Inviting the largest possible group
    4. Reviewing without any preparation

    Explanation

    Review success depends on factors such as clear objectives, appropriate participants, sufficient preparation time, training, and management support for the review process. Large, unprepared groups and a narrow focus on defects undermine effectiveness.

  85. Question 85Static Testing

    Who decides whether reviews will be performed and which review types will be used?

    1. The moderator
    2. The scribe
    3. The review manager Correct answer.
    4. The author

    Explanation

    The review manager has the managerial responsibility for the review process: deciding whether reviews are needed, which types to use, and how resources and time are allocated. The moderator, scribe and author operate within a single review.

  86. Question 86Static Testing

    Which problem is typically detected by static analysis rather than by a review meeting?

    1. A design that does not meet a performance target
    2. A user interface that is hard to navigate
    3. A variable that is declared but never used Correct answer.
    4. An ambiguous requirement

    Explanation

    Static analysis is a tool-based technique applied mostly to code, and it reliably flags constructs such as declared-but-unused variables, unreachable code and violations of coding rules. Judgement-based problems need human reviewers.

  87. Question 87Static Testing

    Which review technique gives reviewers a list of items to check against the work product?

    1. Perspective-based reading
    2. Ad hoc reviewing
    3. Scenario-based reviewing
    4. Checklist-based reviewing Correct answer.

    Explanation

    Checklist-based reviewing supplies reviewers with a set of questions or attributes derived from experience, which are checked systematically against the work product. Ad hoc reviewing has no such structure.

  88. Question 88Static Testing

    What is the purpose of the fixing and reporting activity?

    1. To choose the review technique and the reviewers
    2. To distribute the work product to the participants
    3. To decide whether the review is worth carrying out
    4. To resolve findings and record the outcome Correct answer.

    Explanation

    Fixing and reporting covers the follow-up after the review: defects are corrected, findings are tracked to closure, and the review outcome and metrics are recorded. Choosing techniques and participants belongs to planning.

  89. Question 89Static Testing

    How do entry criteria and exit criteria differ in a review?

    1. Entry criteria concern cost; exit criteria concern the schedule.
    2. Entry criteria are set by the author; exit criteria by the reviewers.
    3. Entry criteria apply before the start; exit criteria before completion. Correct answer.
    4. Entry criteria apply to inspections; exit criteria apply to walkthroughs.

    Explanation

    Entry criteria define what must be true before the review begins, for example that the work product is available and complete enough to review. Exit criteria define what must be true before the review is formally closed, for example that all findings are resolved.

  90. Question 90Static Testing

    Which statement about static analysis is correct?

    1. It can compute complexity metrics without executing the code. Correct answer.
    2. It needs test data to reveal problems in the code.
    3. It can only be used after dynamic testing has finished.
    4. It makes code reviews unnecessary.

    Explanation

    Static analysis examines the code as text or a model, so it can calculate measures such as cyclomatic complexity and nesting depth before anything runs. It complements reviews rather than replacing them.

  91. Question 91Static Testing

    What is the main difference between a review and static analysis?

    1. Static analysis is only used on requirements.
    2. Both require the software to be executed.
    3. Reviews are done by people; static analysis by tools. Correct answer.
    4. Reviews are always performed by tools.

    Explanation

    Reviews are a form of static testing in which people examine a work product, applying judgement and experience. Static analysis is also static testing but is performed by tools that check the work product automatically.

  92. Question 92Static Testing

    What is a limitation of static testing?

    1. It cannot examine documents such as designs.
    2. It always requires a test environment.
    3. It cannot show how the software behaves at run time. Correct answer.
    4. It finds only syntax errors.

    Explanation

    Because static testing never executes the software, it cannot reveal runtime behaviour such as performance, timing, resource consumption or interactions with the environment. Those require dynamic testing.

  93. Question 93Static Testing

    A team wants quick feedback on a prototype screen design from users and the designer, with minimal formality. Which approach fits best?

    1. A technical review run by the database administrators
    2. Static analysis of the interface source code
    3. An informal review with users and the designer Correct answer.
    4. A formal inspection collecting detailed metrics

    Explanation

    An informal review has no defined process or formal recording and is cheap and quick, which suits obtaining early feedback on a prototype from users and the designer. Formal inspections and specialist technical reviews would be disproportionate here.

  94. Question 94Static Testing

    Which statement best describes static testing?

    1. It requires a configured test environment to run the system.
    2. It measures response times while the system is under load.
    3. It executes the software with carefully chosen test data.
    4. It examines work products without executing them. Correct answer.

    Explanation

    Static testing is concerned with examining artifacts such as requirements, design models and source code without running them. Execution of the software belongs to dynamic testing and requires test data and an environment.

  95. Question 95Static Testing

    In a review, which role is responsible for ensuring that the review follows agreed rules and stays focused?

    1. Test manager
    2. Moderator Correct answer.
    3. Author
    4. Scribe

    Explanation

    The moderator leads the review meeting and keeps it on track, ensuring that the agreed review rules are followed and conflicts are handled. The author explains and later fixes the work product, while the scribe records findings.

  96. Question 96Static Testing

    Which review type is primarily concerned with business decisions such as whether a project should proceed to the next phase?

    1. Structured walkthrough
    2. Technical review
    3. Management review Correct answer.
    4. Formal inspection

    Explanation

    A management review is performed by managers to make decisions about planning, progress, resources and whether to continue. It focuses on business and project concerns rather than detailed technical correctness.

  97. Question 97Static Testing

    Reviewers are asked to examine a work product from the viewpoints of an end user, a developer and a tester in turn. Which review technique is being used?

    1. Role-based reviewing Correct answer.
    2. Ad hoc reviewing
    3. Scenario-based reviewing
    4. Checklist-based reviewing

    Explanation

    Role-based reviewing assigns each reviewer a specific stakeholder perspective so that different concerns are examined. Checklist-based reviewing uses predefined checks, scenario-based reviewing uses concrete usage situations, and ad hoc reviewing gives no structured guidance.

  98. Question 98Static Testing

    Which type of static analysis would most directly reveal a section of code that can never be executed?

    1. Control flow analysis Correct answer.
    2. Data flow analysis
    3. Interface analysis
    4. Coding standard analysis

    Explanation

    Control flow analysis examines the possible paths through a program and can identify unreachable code and undesirable control structures. Data flow analysis tracks variables, coding standard analysis checks style rules, and interface analysis checks consistency between components.

  99. Question 99Static Testing

    Which output of a formal review records the findings, decisions and agreed actions?

    1. Coverage report
    2. Review report Correct answer.
    3. Entry criteria
    4. Test log

    Explanation

    The review report is produced from the review and documents the defects found, decisions made and actions agreed. Entry criteria define what must be true before a review starts, while coverage and test logs come from dynamic testing.

  100. Question 100Static Testing

    A static analysis tool reports that a variable may be read before it has been assigned a value. Which analysis produced this finding?

    1. Data flow analysis Correct answer.
    2. Coding standard analysis
    3. Control flow analysis
    4. Cyclomatic complexity measurement

    Explanation

    Data flow analysis tracks where variables are defined and where their values are used, so it can detect anomalies such as use before definition. Control flow analysis deals with possible execution paths, while coding standard analysis checks rules about style and naming.

  101. Question 101Static Testing

    A regulated medical device team must review a software module using a formal, documented process that collects metrics. Which review type is most appropriate?

    1. Informal review
    2. Inspection Correct answer.
    3. Technical review
    4. Walkthrough

    Explanation

    An inspection is the most formal review type, following a defined process with assigned roles, entry and exit criteria, and collected metrics. Walkthroughs and technical reviews are less formal, and informal reviews have no documented process.

  102. Question 102Static Testing

    Which metric is commonly collected from reviews to help evaluate their effectiveness?

    1. Number of defects found per review hour Correct answer.
    2. Statement coverage achieved by the test suite
    3. Number of test cases executed per day
    4. Mean time between failures in production

    Explanation

    Review metrics such as defects found per review hour or per work product page help assess how effective and efficient reviews are. Coverage, failure intervals and test execution counts are dynamic testing or operational measures.

  103. Question 103Test Techniques

    Which test technique divides the input domain into groups whose members are expected to be processed in the same way?

    1. Equivalence partitioning Correct answer.
    2. State transition testing
    3. Boundary value analysis
    4. Decision table testing

    Explanation

    Equivalence partitioning splits the input domain into partitions in which all values are expected to be handled identically, so one representative value per partition is considered sufficient.

  104. Question 104Test Techniques

    Boundary value analysis focuses test cases primarily on which values?

    1. values on the edges of each partition Correct answer.
    2. values taken from the live production system
    3. values chosen at random by the tester
    4. values in the middle of each partition

    Explanation

    Boundary value analysis targets the values at and just around the edges of an equivalence partition, because defects cluster where comparisons and limits are implemented.

  105. Question 105Test Techniques

    Decision table testing is most appropriate when:

    1. the tester has no specification or documentation
    2. inputs must be split into valid groups
    3. behaviour depends on combinations of conditions Correct answer.
    4. the system has many internal states

    Explanation

    A decision table lists conditions and the actions that follow from each combination, so it is used where the required behaviour depends on several conditions acting together.

  106. Question 106Test Techniques

    Which technique models a system as a set of states and the events that cause movement between them?

    1. Error guessing
    2. Equivalence partitioning
    3. Statement testing
    4. State transition testing Correct answer.

    Explanation

    State transition testing represents the system as states plus transitions triggered by events, and test cases are derived from that model.

  107. Question 107Test Techniques

    Error guessing is best described as:

    1. a specification-based technique that uses partitions to derive tests
    2. an experience-based technique based on tester intuition Correct answer.
    3. a formal technique based on state models
    4. a structural technique measuring coverage

    Explanation

    Error guessing is an experience-based technique in which the tester uses knowledge of typical and previously seen defects to anticipate where faults are most likely.

  108. Question 108Test Techniques

    Which statement describes exploratory testing?

    1. Tests are derived from the internal code structure
    2. Tests are designed in advance from a detailed specification
    3. Tests are run only by end users during acceptance
    4. Tests are designed and executed at the same time Correct answer.

    Explanation

    In exploratory testing, test design and execution happen together while the tester simultaneously learns about the system under test.

  109. Question 109Test Techniques

    Use case testing is particularly useful for:

    1. measuring the percentage of statements executed by a test suite
    2. checking values at the edges of partitions
    3. testing end-to-end transactions through the system Correct answer.
    4. counting the independent paths in a module

    Explanation

    Use case testing exercises complete transactions from start to finish, including alternative and exception flows, which makes it effective at finding integration and end-to-end defects.

  110. Question 110Test Techniques

    Which of the following is a white-box test technique?

    1. Use case testing
    2. Decision table testing
    3. Statement testing Correct answer.
    4. Equivalence partitioning

    Explanation

    Statement testing derives tests from the code and measures which statements have executed, which makes it a structure-based, white-box technique.

  111. Question 111Test Techniques

    A field accepts integer values from 10 to 50 inclusive. Using two-value boundary value analysis, which set of values should be tested at the boundaries?

    1. 9, 51
    2. 10, 50
    3. 9, 10, 50, 51 Correct answer.
    4. 10, 30, 50

    Explanation

    Two-value boundary value analysis pairs each boundary with its closest neighbour in the adjacent partition, giving 9 and 10 at the lower boundary and 50 and 51 at the upper boundary.

  112. Question 112Test Techniques

    A username field accepts between 5 and 10 characters. Which set of equivalence partitions is correct?

    1. the exact values 5 characters, 10 characters and 15 characters
    2. under 5 characters, 5-10 characters, over 10 characters Correct answer.
    3. 0-4 characters, 11-20 characters
    4. valid input and invalid input

    Explanation

    Equivalence partitioning requires one partition for each distinct behaviour: too short, of valid length, and too long, because the system treats each of these differently.

  113. Question 113Test Techniques

    A full decision table covers three conditions, each of which can only be true or false, and every combination is possible. How many rules does the table contain?

    1. 3
    2. 9
    3. 6
    4. 8 Correct answer.

    Explanation

    The number of rules in a full decision table is 2 raised to the number of conditions, so three binary conditions give 2^3 = 8 rules.

  114. Question 114Test Techniques

    What does achieving 100% valid transition coverage require?

    1. every path through the model is executed
    2. every invalid transition is executed at least once
    3. every state is visited at least once
    4. each valid transition is executed at least once Correct answer.

    Explanation

    Transition coverage (all transitions) requires every valid transition in the state model to be exercised by at least one test case.

  115. Question 115Test Techniques

    A program contains 100 executable statements. A test suite executes 85 of them. What is the statement coverage achieved?

    1. 85% Correct answer.
    2. 100%
    3. 15%
    4. It cannot be determined from this information

    Explanation

    Statement coverage is the number of statements executed divided by the total number of executable statements, so 85 divided by 100 gives 85%.

  116. Question 116Test Techniques

    Which statement about decision coverage and statement coverage is true?

    1. decision coverage can only be measured using black-box tests
    2. statement coverage and decision coverage always give the same percentage
    3. 100% decision coverage guarantees 100% statement coverage Correct answer.
    4. 100% statement coverage guarantees 100% decision coverage

    Explanation

    Exercising both outcomes of every decision necessarily executes the statements controlled by those decisions, so full decision coverage implies full statement coverage; the reverse does not hold.

  117. Question 117Test Techniques

    When designing test cases with equivalence partitioning, how should invalid partitions be covered?

    1. Invalid partitions are only tested during acceptance testing
    2. Several invalid partitions can be combined in a single test case
    3. Invalid partitions do not need to be tested
    4. One test case should cover only one invalid partition Correct answer.

    Explanation

    Combining several invalid values in one test case can mask which invalid condition caused a failure or prevented later checks from running, so each invalid partition is covered by its own test case.

  118. Question 118Test Techniques

    In use case testing, what does the basic flow represent?

    1. the most common path with no exceptions Correct answer.
    2. a path taken only when an error occurs
    3. a path that is never exercised in testing
    4. the set of all possible paths through the use case

    Explanation

    The basic flow, or happy path, is the most typical sequence of steps that completes successfully; alternative and exception flows branch away from it.

  119. Question 119Test Techniques

    Which is a characteristic of session-based exploratory testing?

    1. Test cases are written in full before execution
    2. Sessions are run without any documentation at all
    3. Coverage is measured only with statement coverage
    4. Work is time-boxed into sessions with a charter Correct answer.

    Explanation

    Session-based exploratory testing is time-boxed into sessions, each guided by a charter that defines what to explore and what deliverables are expected.

  120. Question 120Test Techniques

    Checklist-based testing is best described as:

    1. structure-based, measuring path coverage
    2. specification-based, deriving tests from a state model
    3. a technique that replaces all other design techniques
    4. experience-based, using a list of items to check Correct answer.

    Explanation

    Checklist-based testing is experience-based: the tester works through a list of items derived from experience to decide what to test and to evaluate the results.

  121. Question 121Test Techniques

    Why does boundary value analysis concentrate on partition edges?

    1. Defects are more likely at boundaries than in the middle Correct answer.
    2. Boundaries are tested only for valid partitions, not for invalid ones
    3. Every value inside a partition must be tested individually
    4. Boundary testing can only be applied to numeric fields

    Explanation

    Boundary value analysis targets partition edges because comparison and off-by-one errors cluster there, while values deep inside a partition are less likely to expose defects.

  122. Question 122Test Techniques

    Which statement best describes the difference between black-box and white-box techniques?

    1. Black-box techniques require code coverage measurement to be effective
    2. Black-box uses the specification; white-box uses the structure Correct answer.
    3. White-box techniques can be applied without any knowledge of the code
    4. Both techniques rely mainly on reviewing the source code

    Explanation

    Black-box techniques derive tests from the specification or other external descriptions, whereas white-box techniques derive them from the internal structure such as code or architecture.

  123. Question 123Test Techniques

    A function contains two consecutive IF statements, each with a single condition and no ELSE branch. What is the minimum number of test cases needed to achieve 100% decision coverage?

    1. 1
    2. 3
    3. 4
    4. 2 Correct answer.

    Explanation

    Each decision must evaluate both true and false at least once; one test case where both conditions are true and one where both are false achieves this, so two test cases are the minimum.

  124. Question 124Test Techniques

    A program contains statements S1, S2 and S3 inside an IF-THEN block that runs when X > 0, plus statement S4 after the block, which always executes. A single test with X = 0 is run. What statement coverage is achieved?

    1. 25% Correct answer.
    2. 0%
    3. 75%
    4. 33%

    Explanation

    Four executable statements exist in total. With X = 0 only S4 executes, so coverage is 1 out of 4, which is 25%.

  125. Question 125Test Techniques

    A state model has states S1, S2 and S3 with valid transitions S1 to S2, S2 to S3, S3 to S1 and a self-loop on S2. What is the minimum number of test cases needed for 100% valid transition coverage?

    1. 4
    2. 3
    3. 1 Correct answer.
    4. 2

    Explanation

    A single test case can follow S1 to S2, take the self-loop on S2, continue S2 to S3 and then S3 to S1, exercising all four valid transitions, so one test case is the minimum.

  126. Question 126Test Techniques

    A decision table has four conditions, each able to take the values true or false. One combination, all four false, is impossible in practice and is removed. How many rules remain?

    1. 8
    2. 16
    3. 12
    4. 15 Correct answer.

    Explanation

    A full table with four binary conditions has 2^4 = 16 rules; removing the single impossible combination leaves 15 rules.

  127. Question 127Test Techniques

    Testing must cover a system where the discount a customer receives depends on combinations of several business rules, and where the outcome also depends on the sequence of screens the customer passes through. Which combination of techniques is most appropriate?

    1. decision table testing and state transition testing Correct answer.
    2. boundary value analysis and error guessing
    3. equivalence partitioning and checklist-based testing
    4. statement testing and decision testing

    Explanation

    Combinations of business rules are modelled systematically by decision tables, and a sequence of screens the user moves through is naturally modelled as states and transitions.

  128. Question 128Test Techniques

    What is the main principle of equivalence partitioning?

    1. Inputs are split into groups processed the same way, and one value from each group is tested. Correct answer.
    2. Test values are chosen only at the edges of the input range.
    3. Tests are derived from the internal code structure, measuring which statements and decisions have been executed.
    4. Every possible input value is tested at least once, including values in the middle of each range.

    Explanation

    Equivalence partitioning divides the input domain into partitions whose values are expected to be treated identically by the system. Testing one representative value from each valid and invalid partition reduces the number of test cases while still covering the behaviour.

  129. Question 129Test Techniques

    In a decision table, what does each column represent?

    1. One individual condition with its expected result
    2. A single test environment
    3. A state of the system under test together with its allowed transitions
    4. A rule combining conditions with the actions to take Correct answer.

    Explanation

    A decision table lists conditions and actions; each column is a rule that combines condition values with the actions to take. Rules are derived so that every relevant combination is represented.

  130. Question 130Test Techniques

    Error guessing is a test technique that relies mainly on which of the following?

    1. A checklist supplied by the customer and reviewed before each test session
    2. The internal control flow of the code
    3. The tester's experience and knowledge of typical defects Correct answer.
    4. A formal model of the system's states

    Explanation

    Error guessing is an experience-based technique in which the tester uses knowledge of typical mistakes and past defects to anticipate where failures are likely. It is not based on a formal model or on code structure.

  131. Question 131Test Techniques

    A field accepts whole numbers from 1 to 100 inclusive. Using three-value boundary value analysis, which set of values tests the lower boundary?

    1. 0, 1, 100, 101
    2. 0, 1, 2 Correct answer.
    3. 1, 50, 100
    4. 1, 2, 3

    Explanation

    Three-value boundary value analysis tests the boundary itself and the values immediately on each side. For a lower boundary of 1, that gives 0 (just outside), 1 (on the boundary) and 2 (just inside).

  132. Question 132Test Techniques

    In exploratory testing, what is the purpose of a test charter?

    1. It states the mission and scope for a time-boxed exploratory test session. Correct answer.
    2. It lists every path through the source code that must be executed.
    3. It records the exact expected result for each predefined test step and its actual result.
    4. It defines the entry and exit criteria for the whole test level.

    Explanation

    A test charter gives the mission and scope for an exploratory testing session and is usually time-boxed. It guides what to explore without prescribing exact test steps.

  133. Question 133Test Techniques

    In use case testing, what does an alternative flow describe?

    1. The most common sequence of steps that achieves the business goal of the use case
    2. A sequence that must never be allowed to occur because it would corrupt stored data
    3. A valid sequence that differs from the main flow, often handling an exception or option Correct answer.
    4. The sequence of states that the system passes through after a failure has been detected by a monitor

    Explanation

    A use case has a basic flow that achieves the goal and alternative flows that branch off for valid variations or exceptions. Alternative flows are still expected behaviour and should be tested.

  134. Question 134Test Techniques

    A system's behaviour depends on its current mode, and certain actions are only allowed in particular modes. Which technique is most appropriate for designing tests?

    1. Decision table testing of business rules
    2. Equivalence partitioning of input ranges
    3. State transition testing Correct answer.
    4. Statement coverage

    Explanation

    When behaviour depends on the current mode and on which events are allowed in that mode, the system is naturally modelled as a state machine. State transition testing derives tests from states, events and transitions.

  135. Question 135Test Techniques

    A state transition model is tested with a suite that executes every state and every valid transition at least once. Which statement is true?

    1. The suite achieves 100% decision coverage.
    2. The suite achieves 100% transition-pair coverage.
    3. It achieves transition coverage but not necessarily transition-pair coverage. Correct answer.
    4. The suite guarantees that every possible sequence of two consecutive transitions has been exercised.

    Explanation

    Transition coverage requires every valid transition to be executed at least once, and state coverage requires every state to be visited. Executing each transition once does not guarantee that every pair of consecutive transitions has been exercised.

  136. Question 136Test Techniques

    A decision table has three binary conditions. The rules in which condition C1 is false all lead to the same action, regardless of C2 and C3. In a collapsed decision table, how many rules can represent these cases?

    1. Four rules, one for every combination of C2 and C3
    2. Eight rules, one for each combination of the three binary conditions
    3. One rule with don't-care entries for C2 and C3 Correct answer.
    4. Two rules, one for C2 true and one for C2 false

    Explanation

    Collapsing a decision table merges rules that have the same action and differ only in conditions that do not affect that action. Those conditions are marked as don't care, so all combinations with C1 false become a single rule.

  137. Question 137Test Management

    What is a primary benefit of independent testing?

    1. Developers no longer need to perform any testing of their own code.
    2. Testing can be completed without any documented test basis.
    3. Testers are more likely to question developer assumptions. Correct answer.
    4. The number of test cases required is always reduced.

    Explanation

    Independent testers bring a different perspective and are less likely to share the assumptions and blind spots of the people who wrote the code. Independence complements, but never replaces, testing performed by developers. It also does not remove the need for a test basis or reduce the number of test cases needed.

  138. Question 138Test Management

    Which activity is typically the responsibility of a test leader rather than a test manager?

    1. Coordinating the work of test analysts and testers. Correct answer.
    2. Approving the overall project schedule.
    3. Deciding the budget for the whole test project.
    4. Selecting the organizational test policy.

    Explanation

    A test leader focuses on the day-to-day direction of the test team, including planning and coordinating the work of test analysts and testers. Budgets, project schedules and organizational test policy sit at a higher management level.

  139. Question 139Test Management

    In risk management for testing, what is a product risk?

    1. A risk that a product may fail to meet its intended use. Correct answer.
    2. A risk that the test environment will be delivered late.
    3. A risk that the project will exceed its agreed budget.
    4. A risk that a key team member will leave the project.

    Explanation

    Product risks concern the quality of the delivered product, for example defects that could cause failures, poor usability or harm to users. Project risks concern the management and control of the project, such as budgets, staffing and environment delivery.

  140. Question 140Test Management

    What best describes exit criteria?

    1. Conditions that must be met before a test phase begins.
    2. Conditions that must be met to declare a test phase complete. Correct answer.
    3. The schedule that lists when each test case will be executed.
    4. The set of test cases chosen to cover the riskiest requirements.

    Explanation

    Exit criteria define what must be achieved for a test phase to be considered finished, for example coverage targets, defect thresholds or passing regression tests. They are used together with entry criteria to control the start and end of test activities.

  141. Question 141Test Management

    Which item is normally included in a defect report?

    1. The estimated cost of the whole test project.
    2. The personal opinion of the tester about the developer.
    3. The complete source code of the affected module.
    4. Steps that reproduce the observed failure. Correct answer.

    Explanation

    A defect report records what was observed and how to reproduce it, together with expected and actual results, environment details and severity or priority. It is a factual record used by those who must analyze, fix and retest the defect.

  142. Question 142Test Management

    What is the main purpose of a test plan?

    1. To list every defect found during test execution.
    2. To define the coding standards used by developers.
    3. To describe test objectives, approach and resources. Correct answer.
    4. To record the detailed results of each executed test case.

    Explanation

    A test plan documents what is to be tested, why, how, by whom and when, covering objectives, approach, resources, schedule and risks. Detailed results and defects are recorded elsewhere, in test logs and defect reports.

  143. Question 143Test Management

    In defect management, what does the priority of a defect indicate?

    1. How urgently the defect should be fixed relative to others. Correct answer.
    2. The degree of impact the defect has on the system's operation.
    3. The amount of time the tester spent finding the defect.
    4. The number of test cases that failed because of the defect.

    Explanation

    Priority reflects the order or urgency in which a defect should be fixed and is usually agreed with stakeholders. Severity, by contrast, describes the impact of the defect on the system, and the two values can differ.

  144. Question 144Test Management

    What is the purpose of test monitoring?

    1. To approve changes to the configuration items under test.
    2. To decide which defects should be assigned to which developer.
    3. To design new test cases for requirements that are not yet covered.
    4. To compare actual test progress against the planned progress. Correct answer.

    Explanation

    Test monitoring gathers and compares information about actual progress against the plan, providing visibility of status such as coverage, defect levels and effort. The comparison then feeds test control, where corrective actions are decided.

  145. Question 145Test Management

    A project has limited time and a large number of requirements. Which approach is most appropriate for allocating test effort?

    1. Test only the requirements that were added most recently.
    2. Postpone all testing until the complete system is available.
    3. Concentrate testing on the areas with the highest risk. Correct answer.
    4. Test every requirement with an equal number of test cases.

    Explanation

    Risk-based testing allocates effort in proportion to the likelihood and impact of potential failures, so the most important areas receive attention first when time is tight. Equal coverage ignores risk, and testing only recent changes overlooks critical existing functionality.

  146. Question 146Test Management

    Which action addresses a project risk rather than a product risk?

    1. Reviewing the design of a module that handles payments.
    2. Reserving a backup test environment in case the main fails. Correct answer.
    3. Increasing coverage of a complex calculation algorithm.
    4. Adding extra test cases for a feature that may crash under load.

    Explanation

    Project risks relate to the management and control of the project, such as resources, schedules and environments, so a contingency for a failing test environment is a project risk action. The other options all concern possible defects or quality shortcomings in the product itself.

  147. Question 147Test Management

    A test manager must estimate effort but has no historical data from similar projects. Which estimation approach is most suitable?

    1. Extrapolation from the number of defects found so far.
    2. Metrics-based estimation using past project data.
    3. Expert-based estimation using team members' experience. Correct answer.
    4. Estimation based on the ratio of testers to developers.

    Explanation

    Expert-based estimation relies on the knowledge and experience of the people involved and is appropriate when historical data is unavailable. Metrics-based estimation depends on data from previous similar projects, which this situation lacks.

  148. Question 148Test Management

    A test phase is due to start, but the entry criteria have not been met. What is the most appropriate control action?

    1. Begin execution anyway and log the missing items as defects.
    2. Ignore the entry criteria because they are only advisory.
    3. Cancel the test phase permanently.
    4. Raise the issue with stakeholders and decide how to proceed. Correct answer.

    Explanation

    When entry criteria are not met, the situation should be made visible and discussed with stakeholders, who may accept a deviation, delay the start or change the approach. Entry criteria exist to prevent wasted effort and unreliable results.

  149. Question 149Test Management

    A test team needs to identify which version of a requirement a test case was written against. Which configuration management activity supports this?

    1. Scheduling the test execution order.
    2. Estimating the effort needed to execute the test cases.
    3. Recording traceability between configuration items and versions. Correct answer.
    4. Assigning severity levels to reported defects.

    Explanation

    Configuration management identifies, controls and records versions of configuration items such as requirements and test cases, and maintains traceability between them. This allows the team to see exactly which version a test case was based on.

  150. Question 150Test Management

    A defect causes a minor cosmetic error on a rarely used screen, but the customer requires it fixed before release. How should it be recorded?

    1. Low severity and low priority.
    2. High severity and low priority.
    3. Low severity and high priority. Correct answer.
    4. High severity and high priority.

    Explanation

    Severity reflects the impact on the system, which is minor here, while priority reflects the urgency of fixing, which the customer's requirement makes high. Severity and priority are assessed separately and often differ.

  151. Question 151Test Management

    Which situation gives the highest level of test independence?

    1. A tester from an independent test team in the same organization.
    2. A developer tests the code they wrote themselves.
    3. A developer in the same team tests a colleague's code.
    4. An external consultant hired to test the system. Correct answer.

    Explanation

    Independence increases as testers become further removed from the code and its authors, so testers from a different organization give the highest level. Testing your own code is the lowest level, and colleagues and internal independent teams sit in between.

  152. Question 152Test Management

    During execution, the pass rate is far below plan and many defects block progress. Which control action is most appropriate?

    1. Mark the blocked tests as passed to keep the metrics accurate.
    2. Continue executing without change to keep the original schedule.
    3. Re-plan the remaining work and address the blocking defects first. Correct answer.
    4. Stop recording defects so the team can focus on testing.

    Explanation

    Test control responds to monitoring information by taking corrective action, such as re-planning, prioritizing blocking defects or adjusting scope. Ignoring the situation or distorting records hides the problem and produces misleading status reports.

  153. Question 153Test Management

    Test execution is complete and most exit criteria are met, but a few low-risk tests remain unexecuted. What should the test manager do?

    1. Declare the phase complete without informing stakeholders.
    2. Discuss residual risk with stakeholders and agree acceptance. Correct answer.
    3. Delete the remaining tests from the test plan.
    4. Extend the schedule indefinitely until every test is executed.

    Explanation

    When exit criteria are not fully met, the remaining risk should be made transparent and acceptance agreed with stakeholders. This supports an informed release decision rather than an unrecorded deviation or open-ended delay.

  154. Question 154Test Management

    Which responsibility typically belongs to the test manager?

    1. Executing the regression test suite each day.
    2. Writing the detailed test cases for a feature.
    3. Deciding the overall test budget and resource allocation. Correct answer.
    4. Logging defects found during exploratory testing.

    Explanation

    The test manager is accountable for the overall test process, including planning, budgeting, resourcing and reporting. Detailed test design, execution and defect logging are performed by test analysts and testers.

  155. Question 155Test Management

    Which measure best shows test execution progress against the plan?

    1. The number of requirements in the requirements specification.
    2. The number of developers assigned to the project.
    3. The total size of the test data files.
    4. The percentage of planned test cases that have been run. Correct answer.

    Explanation

    Progress reporting compares planned and actual test execution, commonly through the proportion of planned test cases run or passed. The other figures describe inputs or static characteristics and do not reflect execution progress.

  156. Question 156Test Management

    After a developer fixes a defect, what is the typical next step in the defect workflow?

    1. The fix is retested and, if successful, the defect is closed. Correct answer.
    2. The defect is deleted from the defect tracking system.
    3. The defect is reopened immediately without retesting.
    4. The defect is reassigned to the test manager for approval.

    Explanation

    A fixed defect is normally retested to confirm the failure no longer occurs, and the record is closed once the fix is verified. Deleting records loses history, and reopening without a retest is premature.

  157. Question 157Test Management

    Risk A has a 20% likelihood and an impact of 50,000. Risk B has a 40% likelihood and an impact of 10,000. Using risk exposure (likelihood × impact), what should guide test prioritization?

    1. Risk B, because its likelihood is twice that of Risk A.
    2. Both equally, because the sum of likelihood and impact is the same.
    3. Neither, because monetary impact cannot be used in risk analysis.
    4. Risk A, because its risk exposure is higher than Risk B's. Correct answer.

    Explanation

    Risk exposure is calculated as likelihood multiplied by impact, giving 10,000 for Risk A and 4,000 for Risk B. Risk A therefore warrants more test effort despite its lower likelihood, because likelihood alone does not determine the level of risk.

  158. Question 158Test Management

    A test manager estimates effort from the number of test cases, the average time per test case and the team's historical productivity. Which statement about this approach is true?

    1. It can only be used after all tests have been executed.
    2. It is metrics-based and relies on reliable historical data. Correct answer.
    3. It guarantees the estimate will match actual effort exactly.
    4. It is an expert-based technique and needs no historical data.

    Explanation

    This is metrics-based estimation because it derives effort from measured quantities and past productivity data. Its accuracy depends on the relevance and reliability of that historical data, and any estimate carries uncertainty.

  159. Question 159Test Management

    A test plan has been formally approved and baselined. A developer asks to change a requirement that the plan covers. What is the correct configuration management response?

    1. Submit the change to change control so its impact can be assessed. Correct answer.
    2. Change the requirement immediately because development requests take priority.
    3. Create a new test plan for each change request received.
    4. Refuse all changes until the test phase has finished.

    Explanation

    Once an item is baselined, changes must go through formal change control, where the impact on related items such as test cases, plans and schedules is assessed before a decision is made. This preserves integrity and traceability of the baselined configuration.

  160. Question 160Test Management

    Test metrics show that 70% of defects are found in two of twenty modules. How should the test manager use this information?

    1. Remove test cases from the other eighteen modules entirely.
    2. Conclude that the two modules are of low quality and stop testing them.
    3. Report that the product is ready because most modules have few defects.
    4. Focus additional test effort on those two modules. Correct answer.

    Explanation

    Defect clustering indicates that a small number of components carry most of the risk, so additional analysis and test effort should be directed there. The remaining modules still need adequate testing, and defect concentration is evidence of quality problems, not readiness.

  161. Question 161Test Management

    Which consideration most directly affects how much test independence a project should use?

    1. Product risk level and the skills available in the team. Correct answer.
    2. The number of pages in the test plan document.
    3. The programming language used for the test automation scripts.
    4. The colour scheme used in the user interface.

    Explanation

    The appropriate level of independence depends on factors such as the risk of the product, the consequences of failure, and the skills and availability of independent testers. Higher-risk systems usually justify a greater degree of independence.

  162. Question 162Test Management

    Which information is essential in a defect report so that another tester can reproduce the failure?

    1. The steps to reproduce the failure and the environment used Correct answer.
    2. The amount of test effort originally estimated for the test level
    3. The business justification for the project that produced the software under test
    4. The names of all testers who executed tests on the same day

    Explanation

    A defect report must allow someone who was not present to reproduce the failure, so it records what was done and under which conditions (environment, version, data). Severity, priority and status are added as the defect is processed, but reproduction detail is fundamental.

  163. Question 163Test Management

    Which of the following is normally documented in a test plan?

    1. The exit criteria that must be met before testing is complete Correct answer.
    2. The list of source code changes made to fix the reported defects
    3. The pass or fail status recorded for each individual test case
    4. The root cause analysis of every defect found during test execution

    Explanation

    A test plan describes scope, objectives, approach, resources, schedule and the criteria for starting and completing the work, including exit criteria. Detailed results, defect analyses and code changes are produced during execution and stored in other work products.

  164. Question 164Test Management

    A test manager decides the test approach by analysing the likelihood and impact of failures for each feature of the product. Which type of test strategy is being applied?

    1. Analytical Correct answer.
    2. Consultative
    3. Methodical
    4. Regression-averse

    Explanation

    Analytical strategies, of which risk-based testing is the classic example, derive the test approach from analysis of the product and its risks. Methodical strategies rely on checklists or failure-based techniques, consultative strategies rely on advice from outside the test team, and regression-averse strategies concentrate on repeated testing of existing areas.

  165. Question 165Test Management

    Three weeks into a planned eight-week test execution phase, the test manager must tell stakeholders about current progress, deviations from the plan and issues that need decisions. Which document is most appropriate?

    1. A test summary report for the completed test level
    2. An updated test plan submitted for formal re-approval
    3. A test status report covering the current period Correct answer.
    4. A defect report for the most severe open defect

    Explanation

    Status or progress reports are issued regularly while a test level is running to compare actual progress with the plan and to raise issues for decision. A test summary report is produced at the end of a level, and a single defect report or plan revision cannot serve this periodic communication purpose.

  166. Question 166Test Management

    A test environment needs realistic data taken from a live production database that holds customers' personal details. What is the most appropriate action before the data is used?

    1. Copy the data unchanged so that the tests stay as realistic as possible
    2. Use only the records of customers who have complained about the system
    3. Restrict the data to testers whose employment contracts are already signed
    4. Anonymise or mask the personal data before it is used Correct answer.

    Explanation

    Test data must comply with data protection legislation, so personal data should be masked or anonymised before it enters a test environment while still keeping the data realistic. Neither contractual arrangements nor selecting a subset of records removes the legal obligation.

  167. Question 167Test Management

    Which activity belongs to the test closure phase?

    1. Executing the regression suite after the final defect fixes
    2. Reviewing the test basis to design the first set of test cases
    3. Assigning defects to developers during a triage meeting
    4. Consolidating the testware so it can be handed over for reuse Correct answer.

    Explanation

    Test closure takes place once execution has finished and covers activities such as archiving testware, handing it over for maintenance and reuse, recording lessons learned and confirming completion. Test design, test execution and defect triage all happen earlier in the life cycle.

  168. Question 168Test Management

    During testing, 80 defects were found. In the first six months after release, users reported 20 further defects. What is the defect detection percentage for the testing that was performed?

    1. 25%
    2. 20%
    3. 80% Correct answer.
    4. 125%

    Explanation

    Defect detection percentage is calculated as defects found in testing divided by all defects found in testing plus after release, multiplied by 100. Here 80 divided by (80 + 20) equals 0.8, so the testing detected 80% of the defects known to exist, which indicates how effective it was.

  169. Question 169Tool Support for Testing

    Which tool category primarily stores and manages requirements, test cases and incident reports, and provides traceability between them?

    1. Test execution tool
    2. Static analysis tool
    3. Test management tool Correct answer.
    4. Performance testing tool

    Explanation

    Test management tools support the management of testware, requirements, incidents and configuration items, and they maintain links between these work products throughout the lifecycle. They do not analyse code or generate load.

  170. Question 170Tool Support for Testing

    A tool inspects source code for violations of coding standards and suspicious constructs without running the program. Which category does it belong to?

    1. Dynamic analysis tool
    2. Static analysis tool Correct answer.
    3. Test execution tool
    4. Test management tool

    Explanation

    Static analysis is performed without executing the code under review, which is what distinguishes it from dynamic techniques. It is typically used by developers before formal testing begins.

  171. Question 171Tool Support for Testing

    Which tool type feeds inputs to the system under test, runs test scripts and compares actual results with expected results?

    1. Debugging tool
    2. Test execution tool Correct answer.
    3. Requirements management tool
    4. Test design tool

    Explanation

    Test execution tools drive the system under test, supply test inputs and record outcomes so that comparisons with expected results can be made. They are the category most associated with test automation.

  172. Question 172Tool Support for Testing

    What is the main purpose of a pilot project when an organisation introduces a test tool?

    1. To confirm that the tool has no purchase cost
    2. To learn about the tool and judge its fit before wider use Correct answer.
    3. To replace all manual testing immediately
    4. To satisfy a contractual obligation to the vendor

    Explanation

    A pilot introduces the tool to a small, representative area so the team can gain experience, evaluate benefits and refine processes before a broad rollout. It reduces the risk of a failed organisation-wide introduction.

  173. Question 173Tool Support for Testing

    Which benefit is most characteristic of test automation compared with manual testing?

    1. Guaranteed detection of every defect
    2. Removal of the need for test design
    3. Elimination of the need for regression testing
    4. Consistent, repeatable execution of the same tests Correct answer.

    Explanation

    Automated tests execute the same steps and checks identically each time, which gives consistency and repeatability that manual execution cannot guarantee. Automation still depends on human-designed tests and correct expected results.

  174. Question 174Tool Support for Testing

    In keyword-driven test automation, what do the test scripts mainly consist of?

    1. SQL statements run against the test database
    2. Keywords that map to actions on the system under test Correct answer.
    3. Recorded mouse and keyboard events only
    4. Executable code written only by developers

    Explanation

    Keyword-driven automation separates the action vocabulary from the implementation, so scripts are sequences of keywords that the underlying framework translates into actions. This lets testers with limited programming skill build and maintain tests.

  175. Question 175Tool Support for Testing

    Which tool supports the generation of test cases and test data from requirements or design models?

    1. Configuration management tool
    2. Test design tool Correct answer.
    3. Incident management tool
    4. Coverage measurement tool

    Explanation

    Test design tools help derive test inputs, test cases and expected results from sources such as requirements, design models or code. They assist the design activity rather than execution or version control.

  176. Question 176Tool Support for Testing

    Which is a typical risk when an organisation introduces a test tool?

    1. Unrealistic expectations of what the tool can achieve Correct answer.
    2. Permanent loss of existing testware
    3. Reduced repeatability of regression tests
    4. Inability to run tests manually in future

    Explanation

    Overstated expectations about tool capability are a recognised risk, often leading to disappointment and abandonment of a tool that could have delivered value. Realistic objectives and a pilot mitigate this risk.

  177. Question 177Tool Support for Testing

    Before evaluating specific test tools, what should an organisation do first as part of tool selection?

    1. Train all testers in scripting languages
    2. Assess its own test maturity and identify clear requirements for the tool Correct answer.
    3. Obtain price quotes from at least three vendors
    4. Run a pilot using the most widely used tool on the market

    Explanation

    Tool selection starts with understanding the organisation's current maturity and the improvements it wants, which then drive clear, prioritised requirements for the tool. Only against such requirements can candidate tools be compared objectively.

  178. Question 178Tool Support for Testing

    Which factor contributes most to the successful deployment of a test tool?

    1. Introducing the tool to every team simultaneously
    2. Choosing the tool with the largest feature list
    3. Rolling out incrementally with training and coaching Correct answer.
    4. Delegating all tool decisions to the vendor

    Explanation

    Success depends on incremental introduction, with training, coaching and process adaptation so that people can use the tool effectively. Feature count alone does not create value if the tool does not fit the organisation's needs.

  179. Question 179Tool Support for Testing

    Automated regression tests need heavy rework after every graphical interface change. Which action best addresses the root cause?

    1. Assign more testers to repair the scripts
    2. Increase the number of recorded test scripts
    3. Isolate interface details from the test logic Correct answer.
    4. Run the regression suite less frequently

    Explanation

    Scripts that embed interface specifics break whenever the interface changes. Separating the test logic from the interface layer, for example through keywords or an abstraction layer, confines changes to a small part of the suite.

  180. Question 180Tool Support for Testing

    What is the key characteristic of a data-driven test automation approach?

    1. Only manual test cases can be automated
    2. Scripts are generated from state models
    3. Keywords are defined by the system under test
    4. Test data is held separately from the script logic Correct answer.

    Explanation

    In data-driven automation the same script logic is executed with different sets of input and expected values held externally, for example in a spreadsheet or database. This increases reuse of the script and simplifies adding new data combinations.

  181. Question 181Tool Support for Testing

    Why do capture/replay tools often produce automation that is difficult to sustain?

    1. Recorded scripts are brittle and embed fixed values and screen positions Correct answer.
    2. They only operate on the output of static analysis
    3. They require the system under test to be recompiled
    4. They cannot execute tests without an attached debugger

    Explanation

    Captured scripts record exact events, coordinates and literal values, so small changes in the interface or data break them. Without abstraction and parameterisation they are costly to maintain and yield little reuse.

  182. Question 182Tool Support for Testing

    A team wants objective evidence of which parts of the source code their tests actually exercised. Which tool category provides this?

    1. Static analysis tool
    2. Test management tool
    3. Coverage measurement tool Correct answer.
    4. Performance testing tool

    Explanation

    Coverage measurement tools instrument the code during execution and report which statements, branches or decisions were reached by the tests. The resulting gaps guide additional test design.

  183. Question 183Tool Support for Testing

    What is essential for a performance testing tool to produce meaningful results?

    1. A realistic load profile reflecting expected usage Correct answer.
    2. Switching off all monitoring during the run
    3. Replacing all test data with random values
    4. Executing the load only from a developer workstation

    Explanation

    Results are only useful if the generated load resembles the expected number of users, transaction mix and data volumes. Unrealistic load models produce measurements that do not predict production behaviour.

  184. Question 184Tool Support for Testing

    Which tool capability best supports impact analysis when a requirement changes?

    1. Generation of code coverage reports
    2. Automated assignment of defect severity
    3. Bidirectional traceability between requirements and tests Correct answer.
    4. Recording of test execution durations

    Explanation

    Traceability links each requirement to the tests that verify it, so a change can be followed to the affected testware and vice versa. This makes the impact of change visible before rework begins.

  185. Question 185Tool Support for Testing

    A team adopts an open-source test tool to avoid licence fees. Which cost is most likely to remain significant?

    1. Per-seat licence renewal
    2. Training and ongoing support effort Correct answer.
    3. An annual maintenance contract with the vendor
    4. Compulsory hardware upgrade charges

    Explanation

    With open-source tools the licence cost is low or absent, but effort for training, internal support, configuration and maintenance typically remains and is often underestimated. These hidden costs belong in any cost-benefit analysis.

  186. Question 186Tool Support for Testing

    Which tool would a team use to control versions of test scripts and test data across several testers?

    1. Configuration management tool Correct answer.
    2. Test execution tool
    3. Load generation tool
    4. Static analysis tool

    Explanation

    Configuration management tools provide version control, baselining and controlled change of testware, so that team members work with consistent versions. They also support rebuilding consistent test environments.

  187. Question 187Tool Support for Testing

    Which factor is commonly underestimated when an organisation introduces test automation?

    1. The effort needed to maintain the automated tests Correct answer.
    2. The size of the requirements specification
    3. The number of manual testers still required
    4. The length of the daily progress meeting

    Explanation

    Automated tests must be updated as the system under test evolves, and this maintenance effort is frequently underestimated when benefits are projected. Ignoring it distorts the expected return on investment.

  188. Question 188Tool Support for Testing

    What is the role of monitoring tools during testing?

    1. They replace the test execution tool
    2. They generate test cases from requirements
    3. They observe resource usage and system behaviour during a run Correct answer.
    4. They log defects into the incident register

    Explanation

    Monitoring tools collect data about memory, processor, network and other behaviour while the system is exercised, which helps identify the cause of failures and performance problems. They complement rather than replace other tool types.

  189. Question 189Tool Support for Testing

    An organisation uses separate tools for requirements, test management and defect tracking, and staff re-enter the same data in each. What is the most appropriate improvement?

    1. Assign the re-entry work permanently to one administrator
    2. Replace the tools with independent spreadsheets
    3. Reduce the number of test cases to cut the entry effort
    4. Adopt tools with interfaces that allow the data to be shared Correct answer.

    Explanation

    Poor integration between tools causes duplicated effort and inconsistent data. Selecting tools that can exchange information, or that cover several activities in one platform, removes the duplication at its source.

  190. Question 190Tool Support for Testing

    Which statement best reflects the cost-benefit position of test automation over time?

    1. Costs fall steadily from the first day the tool is used
    2. Benefits are independent of how often the tests are executed
    3. Benefits appear immediately after the tool has been purchased
    4. Costs usually outweigh benefits until tests are reused many times Correct answer.

    Explanation

    Initial investment in the tool, training, framework and script creation usually exceeds the savings at first. Benefits accumulate only once tests are run repeatedly, for example in regression cycles.

  191. Question 191Tool Support for Testing

    What is a key prerequisite for effective model-based testing?

    1. A complete set of recorded manual test scripts
    2. An accurate model of the expected system behaviour Correct answer.
    3. A dedicated performance test environment
    4. A production database containing live customer data

    Explanation

    Model-based testing tools derive test cases from a model of the required behaviour, so the quality of the generated tests depends directly on the accuracy and completeness of that model. An inaccurate model yields tests that either miss behaviour or expect the wrong results.

  192. Question 192Tool Support for Testing

    A static analysis tool produces many warnings that, on review, are harmless. What is the most appropriate response?

    1. Disable the tool and rely on manual reviews alone
    2. Ignore every warning the tool produces from now on
    3. Treat every warning as a confirmed defect
    4. Tune the rule set and review the remaining warnings Correct answer.

    Explanation

    False positives are a known limitation of static analysis, and excessive noise causes teams to stop using the tool. Calibrating the rules to the project's coding standards keeps the output actionable while retaining genuine defect detection.

  193. Question 193Tool Support for Testing

    Why should testers be involved in selecting a test tool?

    1. They control the organisation's procurement budget
    2. They understand the testing process the tool must support Correct answer.
    3. They are responsible for the vendor's product roadmap
    4. They can waive the need for a pilot project

    Explanation

    Testers know how test design, execution, traceability and reporting actually work in the organisation, so they can judge whether a tool fits those activities. Their early involvement also builds the commitment needed for adoption.

  194. Question 194Tool Support for Testing

    Which type of test tool helps a tester decide whether a test has passed or failed by contrasting what the software actually produced with what was expected?

    1. A configuration management tool
    2. A structural coverage measurement tool
    3. A test comparison tool (test oracle) Correct answer.
    4. A performance measurement tool

    Explanation

    Test comparison tools, often called test oracles, take the actual results captured during execution and compare them with the expected results, flagging any differences. They are particularly valuable where output is voluminous, such as log files, batch reports or large data extracts, because manual checking would be slow and error-prone.

  195. Question 195Tool Support for Testing

    Once a test tool has been selected and purchased, what is the main purpose of running a pilot project with it?

    1. To replace the existing test process with the process built into the tool
    2. To gain practical experience and confirm the expected benefits before wider roll-out Correct answer.
    3. To negotiate a lower licence price with the vendor before the purchase is finalised
    4. To train the whole testing organisation in a single intensive session

    Explanation

    A pilot introduces the tool into a real project so the team can learn how it behaves in practice, assess whether the anticipated benefits and costs are realistic, and identify what process or organisational changes are needed. Its findings feed the decision on whether, and how, to deploy the tool across the organisation.

  196. Question 196Tool Support for Testing

    A test manager needs to plan which test cases will run in each release cycle and then record their outcomes against that plan. Which tool category best supports this work?

    1. A load generation tool
    2. A configuration management tool
    3. A coverage measurement tool
    4. A test management tool Correct answer.

    Explanation

    Test management tools support the planning, scheduling and control of test activities, including assigning test cases to cycles, tracking execution status against the plan, and reporting progress and results. This gives management the visibility needed to steer testing across releases.

  197. Question 197Tool Support for Testing

    A team suspects a build intermittently leaks memory and leaves pointers uninitialised, faults that become visible only while the software is running. Which tool type is intended to expose such faults?

    1. A requirements management tool
    2. A dynamic analysis tool Correct answer.
    3. A static analysis tool
    4. A test design tool

    Explanation

    Dynamic analysis tools observe the software as it executes and therefore detect runtime behaviour such as memory leaks, resource misuse and uninitialised pointers. Static analysis examines the code without executing it, so faults that only manifest during execution are outside its reach.

  198. Question 198Tool Support for Testing

    A team wants to exercise a single module repeatedly with automated checks before the modules it depends on have been written. Which term describes the tool support that supplies a way to call the module and to stand in for the missing parts?

    1. A capture/replay tool providing a script library
    2. A defect tracking tool providing a workflow model
    3. An instrumented build providing coverage data
    4. A test harness providing a driver and stubs Correct answer.

    Explanation

    A test harness is the collection of tool support that lets a component be exercised automatically; a driver invokes the component under test and stubs replace the components it calls that are not yet available. This allows unit-level testing to proceed independently of the rest of the system.

  199. Question 199Tool Support for Testing

    An organisation wants to test with a copy of production data but must first remove personal information from it. Which tool support addresses this need?

    1. A static analysis tool that inspects the database schema
    2. A configuration management tool that stores the data sets
    3. A test data preparation tool that masks or anonymises values Correct answer.
    4. A test execution tool that replays recorded user sessions

    Explanation

    Test design and implementation tools include test data preparation tools, which create, extract, edit and transform data for testing. They can mask or anonymise confidential values so realistic production-like data can be used without breaching privacy obligations.

  200. Question 200Tool Support for Testing

    Which statement about custom-built test tools is most accurate?

    1. They are cheaper than commercial tools in every phase of their life cycle
    2. They never need version control because only one team uses them
    3. They need maintenance, support and documentation like any other software Correct answer.
    4. They avoid the need for a pilot project because their requirements are already known

    Explanation

    A bespoke tool is still a software product, so it must be planned, documented, placed under change control and maintained as the system under test evolves. Organisations that ignore this typically find the total cost of ownership far exceeds the initial development effort.

ISTQB Foundation flashcards

32 cards. Read the term and the definition here. The deck at the top of this page is optional.

Testing
A process that evaluates a work product by generating information about its quality and identifying defects, carried out to provide stakeholders with confidence and information for decisions.
Debugging
The development activity that locates, analyzes, and fixes the cause of a defect after a failure has been observed, distinct from testing, which only reveals the failure.
Error, defect, failure
An error is a human action producing an incorrect result; a defect is a flaw in a work product; a failure is incorrect behavior of a component or system during execution.
Seven testing principles
Testing shows presence of defects, exhaustive testing is impossible, early testing saves cost, defects cluster, tests wear out, testing is context dependent, and absence of errors is a fallacy.
Verification vs validation
Verification checks whether a work product meets specified requirements; validation checks whether it fulfills its intended use and user needs in the actual environment.
Test process activities
Planning, monitoring and control, analysis, design, implementation, execution, and completion are the main activities that structure testing on a project.
Test level
A group of test activities organized around a specific stage of development, such as component, integration, system, or acceptance testing, each with distinct objectives and typical participants.
V-model
A sequential lifecycle model in which each development phase has a corresponding test level, emphasizing early test design and verification at every stage.
Shift left
The practice of performing testing and quality activities earlier in the software lifecycle to find defects sooner, when they are cheaper and easier to fix.
Confirmation testing
Re-executing tests that previously failed to verify that a specific defect has been fixed, also called retesting; it does not check for unintended side effects.
Regression testing
Testing performed after changes to verify that previously working functionality still works and that new defects have not been introduced elsewhere in the system.
Static testing
Testing that does not execute the software; it includes reviews of documents and code and static analysis by tools, aiming to find defects early.
Inspection
The most formal review type, following a defined process with entry and exit criteria, checklists, roles, and documented findings, used for critical work products.
Walkthrough
An informal review in which the author leads reviewers through a work product to gather feedback, find defects, and build shared understanding.
Review roles
Manager, author, moderator, scribe, reviewers, and review leader each have defined responsibilities in a formal review, such as planning, recording, and facilitating.
Static analysis
Tool-based examination of code or models without execution, detecting defects such as unreachable code, undefined variables, security flaws, and standards violations.
Equivalence partitioning
A black-box technique dividing input data into partitions where all values are expected to behave the same, so one representative value per partition is tested.
Boundary value analysis
A black-box technique testing values at the edges of equivalence partitions, including the boundary and nearest values on each side, where defects commonly occur.
Decision table testing
A black-box technique using a table of conditions and actions to capture combinations of inputs and expected outcomes, useful for complex business rules.
State transition testing
A black-box technique modeling states, events, and transitions to derive tests that exercise valid transitions, invalid transitions, and all states.
Statement coverage
A white-box coverage measure equal to the percentage of executable statements exercised by tests, calculated as statements executed divided by total statements multiplied by 100.
Exploratory testing
An experience-based approach where testers simultaneously design, execute, and learn from tests, using session-based charters to guide and record their work.
Risk-based testing
A strategy that prioritizes test effort according to product risk, where risk level combines likelihood and impact, focusing testing on the most important areas first.
Product risk
A risk related to the quality of the product itself, such as poor usability, security vulnerabilities, or failure-prone functionality, which guides test prioritization.
Exit criteria
Predefined conditions that must be met before a test level or project phase can be considered complete, such as coverage thresholds or defect resolution rates.
Incident report
A document recording an observed failure or anomaly, including steps to reproduce, expected and actual results, environment details, and severity, used to support defect resolution.
Configuration management
The discipline of identifying, controlling, and tracking versions of testware and software items, ensuring testers use consistent and correctly versioned items.
Test estimation methods
Techniques for predicting test effort, including expert judgment, analogy based on similar projects, and wideband Delphi or planning poker for group consensus.
Test automation benefits
Automated tests can reduce repetitive manual effort, increase execution frequency and consistency, and provide faster feedback, but require investment in design and maintenance.
Tool selection process
Assess organizational needs and constraints, evaluate candidate tools against criteria, conduct a pilot, and then decide whether to adopt the tool.
Test execution tool
A tool that runs test scripts and compares actual results with expected results, often supporting regression testing, test reporting, and continuous integration pipelines.
Test management tool
A tool that supports managing testware, test plans, requirements traceability, execution records, and defects, helping monitor progress and report testing status.

ISTQB Foundation study guide

Fundamentals of Testing

Core concepts

Testing is the process of evaluating a work product to find defects and provide information about quality. Its objectives vary by context: find defects, gain confidence, provide decision information, prevent defects, and satisfy contractual or regulatory requirements. Quality assurance is process-oriented and preventive; quality control is product-oriented and includes testing. Distinguish error (human mistake), defect (fault in a work product), and failure (incorrect behavior during execution). A defect may never cause a failure, and a failure can have a cause outside the tested component.

The test process groups activities: planning; monitoring and control; analysis; design; implementation; execution; and completion. Test conditions are what to test; test cases add inputs, preconditions, and expected results; test procedures order test cases. The seven principles matter: testing shows presence of defects, exhaustive testing is impossible, early testing saves cost, defects cluster, tests wear out (pesticide paradox), testing is context dependent, and absence of errors is a fallacy. Independence helps but does not guarantee better testing.

Traps

Questions often equate testing with debugging, QA with testing, or defect with failure. Testing does not prove correctness; it reduces risk. More testing is not always better without risk focus.

Worked example

A developer types > instead of >= in a length check. The typing slip is an error; the wrong operator in code is a defect; a 6-character name being rejected is a failure. A test observes the failure; debugging locates and fixes the defect.

Rule of thumb: report observed behavior and evidence, not blame.

Testing Throughout the Software Development Lifecycle

Core concepts

SDLC models include sequential (waterfall), iterative, incremental, and Agile. Each affects when and how testing happens. The V-model pairs development activities with test levels: component testing, component integration testing, system testing, system integration testing, and acceptance testing. Test levels differ by objective, test basis, object, typical defects, and responsibility. Test types describe what is tested: functional, non-functional, black-box, white-box, confirmation, regression, and smoke. Confirmation testing checks a specific fix; regression testing checks that changes did not break unaffected areas. Acceptance testing includes user acceptance, operational, contractual, regulatory, alpha, and beta forms.

Shift-left means starting testing early, reviewing requirements and designing tests before code. Agile favors continuous feedback, automation, and whole-team quality. Maintenance testing is triggered by modification, migration, or retirement and begins with impact analysis.

Traps

Candidates mix levels with types, component integration with system integration, and confirmation with regression. Alpha testing occurs at the developer's site; beta at user sites. A test level is not a phase.

Worked example

A tax rate changes. Confirmation testing runs the specific tax calculation with the new rate; regression testing reruns invoice totals, discounts, and reports that depend on tax. Impact analysis decides the regression scope.

Rule of thumb: confirmation = "did we fix this?"; regression = "did we break anything else?"

Static Testing

Core concepts

Static testing examines work products without executing them. It includes reviews and static analysis. Work products include requirements, designs, code, test plans, user stories, and contractual documents. Static testing finds defects early, before dynamic testing can observe failures. Static analysis tools check code for violations such as unused variables, unreachable code, insecure patterns, or complexity.

A formal review follows activities: planning, initiation, individual review, communication and analysis, and fixing and reporting. Roles include manager (decides what and when), moderator (leads), author (creates and fixes), reviewers (inspect), and scribe (records). Review types range from informal to walkthrough (author-led, knowledge sharing), technical review (peer review of technical content), and inspection (formal, moderated, with defined roles and metrics). Success depends on clear objectives, small review scope, trained participants, checklists, and a safe culture.

Traps

Static testing does not find failures because nothing executes; it finds defects. Inspection is the most formal type, not a walkthrough. A technical review is not necessarily led by the author. Reviews are not only meetings; individual preparation is essential. Static analysis is not a substitute for dynamic testing.

Worked example

A reviewer finds the requirement "the system shall respond quickly." This is a defect (ambiguity) in a work product. No execution occurs, so it is static testing. Rewriting it as "95% of searches complete within 2 seconds" makes it testable.

Rule of thumb: no execution means static; execution means dynamic.

Test Techniques

Core concepts

Test techniques help select test conditions and cases. Black-box techniques use specifications: equivalence partitioning divides inputs into classes expected to behave alike; boundary value analysis tests edges; decision tables capture combinations of conditions and actions; state transition testing covers valid and invalid transitions; use case testing exercises user journeys. White-box techniques use structure: statement coverage executes each statement; branch coverage executes each decision outcome; path coverage follows paths but can be infeasible or explode combinatorially. Experience-based techniques include error guessing, exploratory testing, and checklists. Collaboration-based approaches such as ATDD derive tests from examples before implementation.

Technique choice depends on risk, test basis, coverage needs, and context. Coverage measures the proportion of specified items exercised, not proof of quality.

Traps

Candidates confuse equivalence partitioning with boundary values, or assume 100% statement coverage implies 100% branch coverage (it does not). For boundary values, use 2-value or 3-value analysis as specified. Decision tables must cover combinations, not just single rules. State transition tests include invalid events where risk warrants. Path coverage is rarely exhaustive.

Worked example

For valid ages 18–65, equivalence partitions are below 18, 18–65, and above 65. Two-value boundary tests: 17, 18, 65, 66. Three-value boundary tests add 19 and 64: 17, 18, 19, 64, 65, 66. One test per partition is not enough; add boundaries.

Rule of thumb: partition to reduce cases, then boundary-test the edges.

Test Management

Core concepts

Test management covers planning, monitoring and control, and completion. A test plan defines scope, objectives, approach, resources, schedule, risks, and entry/exit criteria. Risk-based testing prioritizes product risks (likelihood × impact) and project risks (schedule, budget, skills). Monitoring compares actual progress with the plan using metrics such as test execution, pass/fail, defect counts, coverage, and defect density; control takes corrective action. Defect management records incidents with reproducible steps, expected and actual results, environment, severity, and priority. Configuration management keeps versions of testware and test items consistent, and traceability links requirements, risks, tests, and defects.

Roles vary: test manager plans and controls; testers analyze, design, and execute; developers fix. Independence can increase objectivity but does not replace developer testing. Entry criteria control when testing starts; exit criteria control when it is complete.

Traps

Risk level is not the same as defect severity. Exit criteria are not the same as a release date. A defect report should be objective and reproducible, not a blame statement. High priority may not mean high severity. Configuration management failures cause wrong-version testing.

Worked example

A payment feature has high likelihood of failure and high business impact, so risk is high. It gets early, broad testing and a strict exit criterion. A cosmetic label has low impact, so fewer tests are proportionate. If a high-risk item is untested, the exit criterion is not met even if the schedule says release.

Rule of thumb: prioritize testing by risk, and prove exit criteria with evidence.

Tool Support for Testing

Core concepts

Test tools support activities across the lifecycle. Categories include test management, requirements management, static analysis, test design and data preparation, test execution and coverage, performance and load, monitoring, and specialized tools. Tools can improve repeatability, speed, coverage measurement, and objective reporting, especially for regression. They also bring risks: unrealistic expectations, underestimated effort for scripting and maintenance, vendor lock-in, compatibility issues, learning curves, and over-reliance.

Tool selection follows a process: identify needs, evaluate options, conduct a proof of concept, pilot in a real project, decide, deploy, and maintain. Automation is a development activity; scripts need design, version control, and maintenance. Record-and-playback is brittle when the UI changes. Open-source tools may have hidden support costs. A tool does not fix a poor process, and it does not replace human judgment.

Traps

Questions claim tools eliminate testers or guarantee quality. Automation is most valuable for stable, repeated tests, not one-off or highly exploratory tests. Tool cost includes training and maintenance, not just license fees. A pilot is not the same as a proof of concept.

Worked example

Manual regression takes 20 hours per week. Automation setup takes 100 hours, and maintenance takes 5 hours per week, leaving 15 hours saved weekly. Break-even is about 7 weeks (100 ÷ 15). If maintenance rises to 18 hours per week, savings disappear and the business case fails.

Rule of thumb: automate stable, high-frequency checks; evaluate total cost of ownership.

ISTQB Foundation cheat sheet

Quick reference

Fundamentals of Testing

  • Testing shows the presence of defects, not their absence; exhaustive testing is impossible, so risk-based prioritization is used.

  • Seven principles: presence of defects, exhaustive testing impossible, early testing, defect clustering, pesticide paradox, context dependence, absence-of-errors fallacy.

  • Cause chain: error (human action) → defect (flaw in a work product) → failure (incorrect behavior during execution); root cause analysis addresses the origin.

  • Verification checks conformance to specified requirements; validation checks fitness for intended use.

  • Test process: planning → monitoring and control → analysis → design → implementation → execution → completion.

  • Test conditions are derived during analysis; test cases and test scripts are created during design and implementation.

  • Testing is product-oriented; quality assurance is process-oriented and focuses on preventing defects.

  • Traceability between test basis, test conditions, test cases, and results supports coverage measurement and impact analysis.

Quick reference

Testing Throughout the Software Development Lifecycle

  • Sequential models such as waterfall and the V-model define distinct phases; iterative and agile models deliver increments with continuous testing.

  • The V-model pairs each development phase with a test level: component, integration, system, and acceptance testing.

  • Component testing checks individual components, often by developers; integration testing checks interfaces and interactions between components or systems.

  • System testing evaluates end-to-end behavior of a complete system against requirements; acceptance testing assesses readiness for deployment and user needs.

  • Shift-left moves test design and static testing earlier, reducing the cost of late defect discovery.

  • Agile testing is whole-team, iterative, and feedback-driven, with practices such as TDD, ATDD, and continuous regression automation.

  • Confirmation testing (retesting) verifies a fix; regression testing verifies that changes did not break unchanged functionality.

  • Maintenance testing is triggered by enhancements, corrections, environment changes, migration, or retirement; impact analysis determines its scope.

Quick reference

Static Testing

  • Static testing does not execute code; it comprises reviews and static analysis and can find defects early in the lifecycle.

  • Review types in increasing formality: informal review, walkthrough, technical review, inspection.

  • Review process: planning, review initiation, individual review, communication and analysis, fixing and reporting.

  • Formal review roles include manager, author, moderator, scribe, reviewers, and review leader.

  • Inspection is the most formal review, uses entry and exit criteria and checklists, and records findings for follow-up.

  • Static analysis detects defects such as unreachable code, undefined variables, inconsistent interfaces, security weaknesses, and standards violations.

  • Reviews are more effective with small chunks, defined objectives, checklists, and participants with appropriate skills.

  • Static testing finds defects that dynamic testing may miss, such as ambiguities in requirements and maintainability issues.

Quick reference

Test Techniques

  • Black-box techniques derive tests from specifications; white-box techniques use internal structure; experience-based techniques use tester knowledge.

  • Equivalence partitioning divides inputs into partitions expected to behave identically; use one value per partition, covering valid and invalid partitions.

  • Boundary value analysis tests each boundary and its nearest neighbors on both sides; boundaries include minimum, maximum, and internal edges.

  • Decision tables capture condition combinations and actions; coverage is measured by the proportion of feasible rules exercised.

  • State transition testing exercises states, events, and transitions; coverage types include all states and all valid transitions.

  • Use case testing derives tests from use case flows, including basic and alternative paths.

  • Statement coverage = (statements executed / total executable statements) × 100%; decision coverage = (decisions exercised / total decisions) × 100%.

  • Experience-based techniques include exploratory testing, error guessing, and checklist-based testing; they complement, not replace, systematic techniques.

Quick reference

Test Management

  • Risk level = likelihood × impact; product risks affect quality, while project risks affect schedule, budget, and resources.

  • Risk-based testing allocates effort to high-risk items first and uses risk to select techniques, coverage, and independence.

  • Test planning defines scope, objectives, approach, resources, schedule, entry and exit criteria, and risks.

  • Test monitoring compares actual progress with the plan; control takes corrective action when deviations occur.

  • Metrics include planned versus actual effort, test case execution, pass and fail rates, defect density, and requirements coverage.

  • Incident reports include identifier, summary, environment, steps to reproduce, expected and actual results, severity, and priority.

  • Configuration management keeps testware and software versions consistent and supports reproducible testing.

  • Test estimation may use expert judgment, analogy, wideband Delphi, planning poker, or three-point estimation.

Quick reference

Tool Support for Testing

  • Tool categories include test management, static testing, test design and implementation, test execution, performance testing, monitoring, and specialized tools.

  • Test execution tools run scripts, compare actual and expected results, and support regression testing and continuous integration.

  • Static analysis tools examine code without execution to detect standards violations, complexity, and security weaknesses.

  • Test management tools support requirements traceability, testware organization, execution tracking, and reporting.

  • Automation reduces repetitive effort but introduces costs for scripting, maintenance, and tool administration; it does not replace human judgment.

  • Tool selection should follow needs assessment, evaluation against criteria, a pilot, and a decision on adoption.

  • Test automation architectures separate test scripts, test libraries, and the system under test to improve reuse and maintainability.

ISTQB Foundation key terms

Testing

The process of evaluating a work product by running it or examining it to find defects, gain information about its quality, and give stakeholders evidence on which to base decisions.

Related: Debugging, Defect
Debugging

The activity developers perform after a test reveals a problem: locating the place in the code that causes it, fixing it, and checking that the fix works.

Related: Defect, Failure
Error

A human mistake or wrong decision, such as a mistyped value or a misunderstood requirement, that puts incorrect information into a work product and may later lead to a defect.

Related: Defect, Failure
Defect

A flaw or imperfection in a work product such as code, a design document or a requirements specification, which can cause the product to fail to do what it should.

Related: Failure, Error, Root cause
Failure

The visible event in which a running system produces a wrong result, crashes or behaves in a way that does not match its specification or the user's reasonable expectation.

Related: Defect, Root cause
Root cause

The underlying reason, often a process or organisational weakness, why a defect was introduced and then not caught; removing it prevents similar defects from coming back.

Related: Defect, Failure
Verification

Checking that a work product was built according to its specification and agreed standards, answering the question of whether the product was built right, often without executing it.

Related: Validation, Static testing
Validation

Checking that the product does what its users actually need in their real situation, answering whether the right product was built, and usually involving users or business representatives.

Related: Verification, Test level
Test level

A group of testing activities organised around a stage of development, such as component, integration, system and acceptance testing, each with its own objectives, test basis and typical defects.

Related: Entry criteria, Exit criteria
Regression testing

Re-running tests on a changed system to check that the change has not broken parts that used to work, often using a growing set of automated tests repeated at every build.

Related: Confirmation testing, Maintenance testing
Confirmation testing

Retesting the specific defect that was reported, using the steps that exposed it, to confirm that the fix really works before the incident is closed.

Related: Regression testing, Defect
Shift left

Doing testing-related activities such as reviews and early test design as early as possible in the lifecycle, because defects found early are cheaper and easier to remove.

Related: Static testing, Test-driven development
Test-driven development

A development approach in which a developer first writes a failing automated unit test, then writes just enough code to pass it, and finally cleans up the code before moving on.

Related: Behavior-driven development, Continuous integration
Behavior-driven development

A team approach that writes tests as readable examples of desired behaviour in business language, so developers, testers and business people agree on what the system should do before coding starts.

Related: Test-driven development, Continuous integration
Maintenance testing

Testing a live system when it is changed, migrated or about to be retired, including checking the change itself and running regression tests on the parts that might be affected.

Related: Regression testing, Test level
Static testing

Examining work products such as requirements, designs and code without executing them, by performing reviews or automated static analysis, in order to find defects early in the lifecycle.

Related: Formal review, Static analysis
Formal review

A structured review that follows defined roles, entry and exit criteria and a documented process, of which the most rigorous type is an inspection.

Related: Inspection, Walkthrough
Walkthrough

An informal review in which the author leads colleagues through a work product to gather feedback, often used to explain a document and find problems quickly.

Related: Formal review, Technical review
Technical review

A review by technically qualified peers who examine a work product against its specification and technical standards, aiming to reach a decision or consensus on technical questions.

Related: Inspection, Formal review
Inspection

The most formal review type: reviewers follow defined rules, check the product against criteria and collect metrics, typically led by a trained moderator who plans the review and follows up.

Related: Formal review, Static analysis
Static analysis

Using tools to examine source code or models for suspicious patterns such as unused variables, unreachable code, security weaknesses or breaches of coding standards, without running the program.

Related: Static testing, White-box testing
White-box testing

Deriving and choosing tests from the internal structure of the code or design, such as statements, branches and paths, rather than from the stated requirements.

Related: Statement coverage, Decision coverage
Equivalence partitioning

Dividing the possible inputs or outputs into groups that the system should treat the same way, then testing one value from each group to reduce the number of cases.

Related: Boundary value analysis, Decision table testing
Boundary value analysis

Testing values at the edges of each equivalence partition, such as the minimum, minimum plus one, maximum and maximum minus one, where developers most often make mistakes.

Related: Equivalence partitioning, Decision table testing
Decision table testing

A technique for combinations of conditions in which the table lists conditions, actions and rules, and each rule becomes at least one test case, revealing gaps other techniques miss.

Related: Equivalence partitioning, State transition testing
State transition testing

Modelling a system as states, events and transitions, then designing tests that cover valid transitions, invalid transitions and sequences of events that change the state.

Related: Decision table testing, Exploratory testing
Statement coverage

A white-box measure and technique: the percentage of executable statements exercised by a set of tests, achieved by designing tests so that every statement runs at least once.

Related: Decision coverage, White-box testing
Decision coverage

A white-box measure and technique: the percentage of decision outcomes, such as each branch of an if statement, exercised by tests, which is stronger than statement coverage.

Related: Statement coverage, White-box testing
Exploratory testing

An experience-based approach in which the tester designs, runs and evaluates tests at the same time, learning about the product as they go and following up on what they discover.

Related: Test plan
Test plan

A document that describes the objectives, scope, approach, resources, schedule and risks of the testing effort, and which is updated as the project progresses.

Related: Entry criteria, Exit criteria
Risk-based testing

Choosing how much and what to test based on the likelihood and impact of potential problems, so that limited effort goes to the areas that matter most to the business.

Related: Product risk, Test plan
Product risk

The chance that the delivered system has a quality problem, such as poor reliability, slow response or a missing feature, which testing tries to reduce by finding related defects.

Related: Risk-based testing, Severity
Entry criteria

Conditions that must be met before a test activity can reasonably start, such as approved requirements, available test data and a working test environment.

Related: Exit criteria, Test plan
Exit criteria

Conditions agreed in advance for declaring a test activity finished, such as reaching a coverage target or having no open critical defects.

Related: Entry criteria, Severity
Severity

The degree of impact a defect has on the system's operation or on stakeholders, rated by the tester, independently of how quickly anyone wants it fixed.

Related: Defect, Product risk
Test automation

Using software tools to run tests, compare actual with expected results and report outcomes, so that repetitive checks can be executed quickly and consistently.

Related: Test execution tool, Continuous integration
Test execution tool

A tool that runs test scripts or test cases against the system under test, records the results and compares them with the expected values.

Related: Test automation, Continuous integration
Performance testing tool

A tool that generates simulated load, such as many virtual users, against a system and measures response times and resource use to support performance and load testing.

Related: Test execution tool, Test automation
Continuous integration

A practice supported by tools in which developers merge their changes frequently and every merge triggers an automated build and test run, so integration problems surface quickly.

Related: Test automation, Test execution tool
Keyword-driven testing

An automation approach in which test steps are written as business keywords in a spreadsheet and a tool translates them into scripts, letting non-programmers create tests.

Related: Test automation, Test execution tool

ISTQB Foundation study plan

8 weeks · About 7 hours per week

Week 1

Fundamentals of Testing

  • Define testing, quality assurance, and debugging, and explain in your own words how they differ

  • Restate all seven testing principles and attach a concrete real-world example to each

  • Sequence the test process activities and name the testware produced by each

  • Explain the psychology of testing, including the tester/developer mindset difference

  • Answer 30 fundamentals practice questions and log every miss with a reason

Your checkpoint

A one-page personal glossary of 15 fundamentals terms plus a closed-book 20-question quiz scored at 80% or higher.

Week 2

Testing Throughout the Software Development Lifecycle

  • Compare sequential and iterative/incremental lifecycle models and name one testing risk for each

  • Describe the test levels (component, integration, system, acceptance) with their objectives, test basis, and typical testware

  • Distinguish functional, non-functional, and white-box test types, giving two examples of each

  • Explain shift-left, the tester's role in DevOps, and the triggers for maintenance testing

Your checkpoint

A test-level matrix covering four levels against objectives, test basis, testware, and roles, plus a 25-question quiz scored at 75% or higher.

Week 3

Static Testing

  • Separate static from dynamic testing and list the work products that can be reviewed

  • Order the review process activities and assign the responsibilities of manager, moderator, author, reviewer, and scribe

  • Compare informal review, walkthrough, technical review, and inspection by formality, objectives, and roles

  • Apply a review checklist to a written requirement snippet and classify each defect found

  • Explain why early static testing is cheaper than finding the same defect later

Your checkpoint

A completed review record for a self-written one-page requirement document: checklist applied, at least five defects logged with type and severity, and the chosen review type justified in three sentences.

Week 4

Test Techniques

  • Derive equivalence partitions and boundary values from an input specification and calculate the resulting test case count

  • Build a decision table and a state transition model for a set of given business rules

  • Calculate statement and branch coverage for a short code snippet and identify the untested branches

  • Choose between black-box, white-box, and experience-based techniques for stated scenarios and justify each choice

Your checkpoint

A technique portfolio of four worked exercises (equivalence partitioning, boundary value analysis, decision table, branch coverage) with computed test counts matching the answer key at 90% or better.

Week 5

Test Techniques & Test Management

  • Complete practice items on experience-based techniques and error guessing with a written rationale for each test chosen

  • Draft a test plan outline covering scope, objectives, approach, entry and exit criteria, and risks

  • Perform a likelihood-by-impact risk analysis on a small feature and rank its tests accordingly

  • Explain how risk level drives the extent of testing and the choice of technique

Your checkpoint

A one-page risk-based test plan for a self-chosen small feature, including a prioritized list of ten tests, each traced to an identified risk.

Week 6

Test Management

  • Interpret test progress and completion metrics such as planned versus executed versus passed, and defect density

  • Describe configuration management and explain how it supports reproducible testing

  • Trace a defect through the standard status workflow from new to closed and to rejected

  • Write defect reports that contain every mandatory field, including steps to reproduce and expected versus actual results

Your checkpoint

Three complete defect reports on a self-written specification plus a metrics summary in which five given data points are interpreted correctly without notes.

Week 7

Tool Support for Testing & Fundamentals of Testing & Static Testing

  • Categorize test tools by the testing activity they support and name two example tools per category

  • State the benefits and the risks of test automation and of tool adoption in an organization

  • Re-take the two lowest-scoring domain quizzes from earlier weeks and correct every missed item in writing

  • Re-verify recall of the seven principles and the four review types without reference material

Your checkpoint

A tool mind map of at least eight categories, each with one benefit and one risk, plus a corrected list of every previously missed question with a one-line reason per item.

Week 8

Fundamentals of Testing & Testing Throughout the Software Development Lifecycle & Static Testing & Test Techniques & Test Management & Tool Support for Testing

  • Complete two full-length timed mock exams under exam conditions with no interruptions

  • Classify every incorrect answer as a knowledge gap, a misread question, or a calculation error

  • Rehearse final recall of coverage formulas, review roles, defect workflow, and test levels

  • Book the exam date and confirm the test-center or remote-proctoring requirements

Your checkpoint

Two full 40-question mocks scored at 75% or higher each, both finished within 60 minutes, with a weak-spot list in which every item is marked resolved.

Milestones

Week 2: Can name all four test levels and their testware without notes, and score 75% or higher on an untimed 25-question domain 2 set.

Week 4: Timed 40-question mock covering domains 1 to 3: score 65% (26/40) or higher within 60 minutes.

Week 6: Compute branch coverage from a code snippet and complete a defect report from memory; domain 4 and domain 5 practice sets each at 75% or higher.

Week 7: All six domain quizzes have been taken at least twice, and no domain sits below 70%.

Week 8: Two consecutive full mocks at 75% or higher within the 60-minute time limit, with no recurring error type.

ISTQB Foundation exam day

Your checklist

Government-issued photo ID

Bring the original document (typically a passport or photo driving licence) in the exact name used on your booking. Confirm which ID types your exam provider accepts before test day - this varies between test centres and online-proctoring platforms.

Exam appointment confirmation

Have the booking confirmation email or candidate/registration number available. For a test-centre sitting it also tells you the exact address and arrival time; for online proctoring it contains the launch link.

Login details for the exam platform

For online proctored exams, verify your username and password work at least 24 hours in advance, and complete any system or identity check the provider asks you to run beforehand.

Compatible computer and stable internet (online sittings)

Run the provider's system test on the same device you will use: webcam, microphone, speakers, browser version and bandwidth. Have a fallback connection (e.g. mobile hotspot) planned.

A quiet, well-lit, private room

Clear the desk of papers, books, phones and notes. A proctor may ask you to pan the camera around the room at the start. Tell household members not to enter during the exam.

Know the exam format

ISTQB Foundation Level is 40 multiple-choice questions in 60 minutes with a 65% pass mark (26 correct answers). Confirm the syllabus version and your specific exam slot length with your provider, since translated or non-native-language sittings may differ.

Confirm any extra-time or access arrangement

Extra time for non-native speakers or reasonable adjustments must normally be requested and approved in advance, not on the day. Check your booking reflects what you requested.

Confirm whether scratch paper or a calculator is permitted

Rules on blank paper, pens and calculators differ between test centres and online proctoring. Ask your provider rather than assuming; assume nothing may be on your desk unless told otherwise.

Water in a clear container

Often allowed, but some proctoring services restrict drinks. Confirm the rule for your delivery method.

A one-page revision sheet for the last look

Use it only in the hours before the exam - not during it. Focus on the keyword lists for each chapter, the test-process terminology and the review/inspection distinctions you keep mixing up.

Plan your route or check-in window

For a test centre, arrive early enough to absorb delays; for online, log in before the start time to complete ID checks and room scan without eating into your 60 minutes.

Plan the day

72 hours before

Stop learning new material. Re-read the syllabus keyword list for each chapter and take one full timed mock exam (40 questions, 60 minutes) under realistic conditions, then review every wrong answer against the syllabus.

48 hours before

Take a second timed mock, focusing on your weakest two chapters. Drill the factual recall items - definitions, test levels, test types, review roles, and the seven testing principles - since these are quick marks.

24 hours before

Re-confirm the appointment time, location or proctoring link, and ID requirements. Prepare your ID and any permitted items in one place. Do a light review of your own error list only; no new mock exams in the evening.

Night before

Set two alarms, charge your device, and get a full night's sleep. A tired candidate misreads 'which is NOT' questions far more often than an under-prepared one.

Morning of

Eat properly, avoid cramming entire chapters, and skim only your condensed notes. Arrive or log in with time to spare; if online, close every other application, silence notifications and put your phone out of reach.

First 2 minutes of the test

Read the instructions, check the question count and timer, and confirm the scratch mechanism (on-screen notes or permitted paper). Note roughly 1.5 minutes per question as your pace.

During the test

Answer in two passes: clear the questions you know immediately, flag anything long or ambiguous, then return to the flagged ones. Read for qualifiers - NOT, EXCEPT, BEST, MOST LIKELY - and eliminate options that are true but do not answer the question asked.

Final 10 minutes

Make sure no question is left blank - there is no penalty for a wrong answer. Re-check that your answers are recorded in the system before submitting, then submit deliberately rather than letting the timer run out.

Rules to check

  • Scoring: all 40 questions carry equal weight with no negative marking, so never leave a blank. You need 65% (26 of 40) to pass; results are typically reported as pass/fail with a percentage and per-chapter breakdown, but confirm what your member board issues.

  • Closed book: no syllabus, notes, textbooks or search tools during the exam. Anything on your desk or screen will be treated as material and may void your result.

  • ID verification: you must present valid photo ID matching your registration. If your ID name differs from the booking, resolve it with the provider before the exam day - do not turn up hoping it will pass.

  • Online sittings are recorded and proctored: follow the proctor's instructions, stay in camera view, keep your face and hands visible, do not read questions aloud, and do not leave the room during the exam.

  • Breaks: for this exam format, breaks are generally not permitted once the clock has started, and leaving the room during an online exam may end your session. Confirm the specific break policy with your provider.

  • If you are disrupted by a technical failure during an online exam, stop and contact the proctor or support line immediately and note the time; do not attempt to fix it silently and continue. Follow their instruction on rescheduling or re-sitting.

  • Rescheduling and cancellation cut-off times, fees and refund rules differ by provider and region. Check your booking terms well before the deadline rather than on the day before.

  • Do not share, photograph or reproduce exam questions afterwards - this breaches the ISTQB Code of Ethics and can invalidate your certification.

ISTQB Foundation FAQ

How many ISTQB Foundation practice questions are available?

The practice set has 200 ISTQB Foundation questions. Each one includes the choices, the correct answer, and an explanation, and the set is free to read with no signup.

How many ISTQB Foundation flashcards are available?

The flashcard set has 32 ISTQB Foundation cards. Each card shows the term and its definition.

Which topics does the ISTQB Foundation study material cover?

The ISTQB Foundation study material has 6 sections, including Fundamentals of Testing, Testing Throughout the Software Development Lifecycle, and Static Testing.

What format facts does the catalog list for the ISTQB Foundation exam?

The catalog lists a duration of 60 minutes and these item types: multiple choice for the ISTQB Foundation exam.