A bank payment engine has a well-specified set of business rules that determine whether a transaction is approved, flagged for review, or declined. Many rules depend on combinations of input attributes (transaction amount, country pair, account status, merchant category). You must design a compact suite of test cases that exercises the rule combinations and clearly documents the expected outcome for each combination. Which test-design technique is the most appropriate choice?
ISTQB Foundation Level — Question Bank
ISTQB_CTFLReady to test yourself?
A timed, blueprint-proportional exam drawn fresh from this bank — with a per-domain score report.
🔓 Free preview: showing 10 of 197 questions. Unlock the full bank — every question, explanation, and reference.
Unlock all 197 questions →10 questions across 6 topics. Choose an answer for each question, then check it to see the correct answer and explanation.
Filter by topic
All 10 questions
Test Analysis and Design
2 questions in topicTest techniques and their categories; black-box techniques — equivalence partitioning, boundary value analysis, decision tables and state transition testing; white-box statement and branch coverage; experience-based error guessing, exploratory and checklist-based testing; and collaboration-based approaches.
A flight-control algorithm implemented in safety-critical embedded C contains many Boolean expressions whose independent evaluation is essential to safety certification. You are required to derive unit tests that can demonstrate that each condition independently affects the decision outcome. Which white-box/structure-based coverage criterion should you select?
Test Tools
8 questions in topicTool support for testing and the benefits and risks of test automation.
You are designing a test tool strategy for a safety-critical embedded application. The objectives include: (1) detecting coding standard violations and certain classes of security vulnerabilities early in development without executing the software, and (2) providing evidence for compliance with coding standards. Which single tool category best meets both objectives?
A system under test has 12 independent input parameters, each with several valid values. The testing team must produce a compact suite that gives high fault-detection effectiveness for interaction faults while keeping case count manageable. Which tool category is the most appropriate primary choice to generate the test inputs?
Your organization runs an automated GUI test suite in the CI pipeline, but tests often fail intermittently due to environment timing and browser differences. The goal is to reduce flakiness and get faster, more reliable pass/fail feedback in CI while still validating user-facing behavior. Which single tooling approach is the best fit?
A test lead asks whether a pure system-level, black-box test execution tool can provide evidence that 90% of statements in the product source code were executed by the test suite. Which statement best describes what coverage information a purely black-box tool can provide without source-code instrumentation?
A team must choose between automating a large suite of end-to-end GUI regression tests that run nightly and automating a smaller set of API-level regression tests that run in every CI pipeline build. Considering long-term return on investment (ROI) and typical maintenance costs, which choice is most likely to deliver the better ROI for a continuous delivery environment?
A product with rapidly changing requirements is moving into a short release cadence. Which risk is most likely to undermine the value of an extensive automated regression suite if automation is introduced immediately without additional measures?
In designing an automation strategy for a system that must support frequent builds and fast feedback, which allocation of automation effort across the test process best balances speed of feedback, cost of maintenance, and overall defect detection capability?
A test automation initiative has produced a large suite of scripts that frequently fail due to minor UI layout changes and inconsistent test data. Which practice, if prioritised, would most directly reduce the number of false failures and the subsequent maintenance load?