Unlock hundreds more features
Save your Quiz to the Dashboard
View and Export Results
Use AI to Create Quizzes and Analyse Results

Sign inSign in with Facebook
Sign inSign in with Google

ISTQB Chapter 1 Mock Test: Check Your Foundation Basics

Quick ISTQB Foundation Level practice test. Instant results.

Editorial: Review CompletedCreated By: Natasha DamodaranUpdated Aug 23, 2025
Difficulty: Moderate
2-5mins
Learning OutcomesCheat Sheet
paper art quiz illustration free ISTQB exam Chapter 1 concepts, requirements correlation, test design, coral background

This ISTQB Chapter 1 mock test helps you check core Foundation Level concepts-terms, roles, objectives, and basic test design-to find weak spots before exam day. Explore our it knowledge test, try the ITIL 4 foundation quiz, and round out your skills with a project management quiz.

Which statement best describes the primary objective of testing in ISTQB Chapter 1 context?
To prove the software is free of defects (Explanation: Testing can show the presence of defects, not their absence).
To reduce the level of risk by finding defects and increasing confidence in the product (Explanation: Core objectives include defect detection and risk reduction).
To ensure developers follow coding standards exclusively (Explanation: That is a quality assurance activity, not the only objective of testing).
To guarantee user acceptance regardless of quality (Explanation: Testing cannot guarantee acceptance).
undefined
In ISTQB terminology, which option correctly matches error, defect, and failure?
Error is a problem in the code; defect is a user complaint; failure is a coding standard violation.
Error is a human mistake; defect is a flaw in a work product; failure is the observable deviation during execution (Explanation: This is the ISTQB-aligned mapping).
Error and failure are synonyms; defect is different.
Error is a runtime crash; defect is an invalid requirement; failure is a tester oversight.
undefined
Which testing principle states that not all defects are uniformly distributed across the system?
Absence-of-errors fallacy.
Testing is context dependent.
Defect clustering (Explanation: Defects tend to cluster in a small number of modules).
Exhaustive testing is possible.
undefined
Which activity primarily belongs to Test Analysis in the fundamental test process?
Executing tests and logging results.
Defining exit criteria.
Archiving testware for reuse.
Identifying test conditions from the test basis (Explanation: Test Analysis derives test conditions).
undefined
Which statement reflects the principle that early testing saves cost and time?
Rely only on dynamic tests late in the lifecycle.
Start testing activities as soon as test basis items are available (Explanation: Early testing reduces defect cost of fix).
Delay reviews until user acceptance begins.
Begin testing only after code freeze to avoid rework.
undefined
Which item typically serves as a test oracle in ISTQB terms?
Developer estimates.
Code coverage reports.
Build scripts.
Documented expected results from requirements or design specifications (Explanation: Oracles determine correct behavior).
undefined
Which best describes the relationship enabled by traceability between requirements and tests?
It eliminates the need for reviews.
It restricts testers to only one level of testing.
It links commits to coding standards.
It allows bidirectional mapping to verify coverage and impact of changes (Explanation: Traceability supports coverage and impact analysis).
undefined
Which role in a formal inspection is primarily responsible for facilitating the session and keeping it effective?
Author.
Scribe.
Moderator (Explanation: The moderator facilitates and ensures the process is followed).
Sponsor.
undefined
Which work product is a typical output of Test Design?
Detailed test cases with preconditions, inputs, and expected results (Explanation: Test Design creates test cases).
Project charter.
Deployment checklist.
Defect trend analysis report.
undefined
Which metric most directly supports monitoring test progress?
Lines of code written.
Percentage of planned test cases executed (Explanation: This indicates progress against plan).
Number of developers onboarded.
Number of commits per day.
undefined
Which best characterizes dynamic testing?
Evaluating the behavior of software by executing it (Explanation: Dynamic tests run the code).
Estimating project budgets.
Assessing artifacts without execution.
Enforcing coding standards in repositories.
undefined
Which measure best indicates requirements coverage by tests?
Number of developers assigned to testing.
Number of test environments available.
Percentage of requirements items linked to at least one test case (Explanation: Traceability supports requirements coverage).
Lines of code executed during tests.
undefined
Which option is the most appropriate source for expected results when designing tests?
Historic defect logs exclusively.
Unverified assumptions of the tester.
Approved specifications and business rules (Explanation: These serve as oracles for expected outcomes).
Team chat discussions only.
undefined
Which is the most suitable review goal for early detection of requirement ambiguities?
Calibrate performance counters.
Find inconsistencies, omissions, and unclear statements in requirements (Explanation: Reviews detect static defects early).
Validate load test environments.
Identify performance hotspots in code.
undefined
Which is the best example of a test monitoring indicator?
Server CPU model.
Meeting attendance count.
Employee satisfaction survey result.
Defect detection percentage trend over time (Explanation: It indicates effectiveness and helps control).
undefined
Which deliverable best supports impact analysis when a requirement changes?
Vacation schedule.
Meeting minutes from last sprint review.
Team org chart.
Requirements-to-tests traceability matrix (Explanation: It shows affected tests for changed items).
undefined
Which item is the most appropriate acceptance criterion related to testing for a user story?
Developer agrees the story is complex.
Names of reviewers.
Defined, testable conditions that specify expected behavior (Explanation: Acceptance criteria guide tests and validation).
Number of lines of code changed.
undefined
In a formal review, what is the scribe's primary responsibility?
Approve changes for implementation.
Defend the design choices.
Lead the discussion and resolve conflicts.
Record defects, decisions, and action items accurately (Explanation: Scribe documents outcomes).
undefined
Which test monitoring view most helps senior stakeholders assess release readiness?
Daily tester attendance.
Coverage against exit criteria and residual risk status (Explanation: Readiness relates to criteria and risk).
Code formatting issues.
Raw execution logs.
undefined
Which pairing best exemplifies product vs. project risk in testing?
Product risk: incorrect tax calculation; project risk: delayed test environment availability (Explanation: Product relates to quality, project to management).
Product risk: team turnover; project risk: memory leak.
Product risk: budget overrun; project risk: missing feature.
Product risk: vendor insolvency; project risk: SQL injection defect.
undefined
0

Study Outcomes

  1. Understand ISTQB Core Concepts -

    Grasp the fundamental principles of software testing as defined in the ISTQB Foundation Level syllabus, ensuring a solid knowledge base for your certification journey.

  2. Apply Test Design Principles -

    Use key test design techniques such as equivalence partitioning and boundary value analysis to create effective test cases in line with ISTQB guidelines.

  3. Correlate Requirements with Test Design -

    Link business and technical requirements to specific test cases, ensuring comprehensive coverage and alignment between the requirements document and your test design.

  4. Analyze Test Artifacts for Coverage -

    Evaluate various test documentation artifacts to identify coverage gaps, improving your ability to deliver thorough and traceable testing outcomes.

  5. Identify Knowledge Gaps -

    Pinpoint areas in which you need further review by tracking your performance on the ISTQB Foundation Level mock test questions and explanations.

  6. Evaluate Exam Readiness -

    Assess your confidence and readiness for the real ISTQB exam through a scored practice session, boosting your ability to perform under timed conditions.

Cheat Sheet

  1. Core Testing Definitions -

    Understand the difference between errors (human mistakes), defects (code anomalies), and failures (observable wrong behavior). For example, a misplaced ">" in an if-statement is an error that may produce a defect and trigger a failure in the application. These definitions form the foundation for your ISTQB practice exam and help you analyze test outcomes precisely.

  2. Seven Testing Principles -

    Memorize the seven principles: exhaustiveness is impossible, early testing, defect clustering, pesticide paradox, context dependence, absence-of-errors fallacy, and testing shows presence of defects. Use the mnemonic "EEPDCA" (Exhaustive, Early, Pesticide, Defect clustering, Context, Absence-of-errors) to recall them during an ISTQB Foundation Level mock test. Each principle guides strategic decisions to make your testing efficient and effective.

  3. Fundamental Test Process -

    The five stages - planning and control, analysis and design, implementation and execution, evaluation and reporting, and closure - mirror PDCA (Plan-Do-Check-Act) for continuous improvement. For instance, in implementation you develop test cases, then execute them and log results during execution. Mastering this cycle boosts your confidence when tackling an ISTQB exam mock test scenario.

  4. Test Levels and V-Model Correlation -

    Map development phases to test levels: unit tests follow the unit design, integration tests match architecture, system tests validate system requirements, and acceptance tests ensure business readiness. Visualize the V-model to trace how each test level corresponds to its development counterpart. This clarity is key for any ISTQB example test question on test level relationships.

  5. Essential Test Documentation -

    Refer to IEEE 829 standards: test plan, design specification, case specification, procedure specification, and summary report. Use a traceability matrix (requirements vs. test cases) to ensure full coverage - for example, R1 maps to TC1, TC2. Proper documentation is critical both in practice and in your ISTQB exam mock test to demonstrate structured, auditable testing.

Powered by: Quiz Maker