Factors that are important to take into account when performing test estimation include: i. The quality of the test basis ii. The availability of test automation iii. The amount of rework required iv. The distribution of testing across several locations The various factors can be grouped by characteristic. Examples of characteristics include:
Correct Answer: B
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus: Product characteristic # quality of the test basis (C = i):The syllabus lists the quality and stability of the requirements/specifications (test basis) as a product-related estimation driver. Test results characteristic # amount of rework (B = iii):Expected rework/defect-fix cycles and their impact on retesting and confirmation testing are identified through past results/defect patterns and directly affect estimates. Test context characteristic # distribution across locations (A = iv):Organizational and logistical context (multiple sites, time zones, communication overhead) influences test effort. Development process characteristic # availability of test automation (D = ii):Process/tooling capability (e.g., presence of automation frameworks) is treated as a development/process factor affecting test efficiency and thus estimation.The syllabus groups estimation drivers into characteristics such as product, development process, test results/history, and test/organizational context, and recommends mapping specific factors to these groups to structure estimation.
TM3 Exam Question 7
For which type of testing would a test manager be involved with establishing benchmarks?
Correct Answer: B
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus: WithinTest Planning(Chapter:Test Planning, Monitoring, and Control), the syllabus describes that the test manager defines the test approach fornon-functional quality characteristics(e.g., performance, load, scalability, reliability). For these, the test manager oftensets or references benchmarks/baselines and success criteria(e.g., response-time thresholds, throughput targets) to evaluate system behavior under specified conditions. Establishing and usingbenchmarksis a hallmark ofnon-functional testing, particularlyperformance testing. (Reference: CTAL-TM v3.0 Syllabus - Chapter "Test Planning, Monitoring, and Control", subsections on defining the test approach for non-functional testing and specifying success criteria/benchmarks.)
TM3 Exam Question 8
Management is sceptical regarding the budget request (€25,000) for the next testing project. You are asked for a cost-benefit calculation. Based on historical data from several projects, you have the following numbers: Average prevention cost per defect: €200 Average cost of detection per defect: €400 Average cost of internal failure: €150 Average cost of external failure: €2,500 Expected number of defects to be found in this project during testing: 50 What is the result for the expected cost-benefit calculation for the upcoming project?
Correct Answer: C
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus: Using thecost of qualityperspective in the syllabus, compute the savings from moving defects fromexternal failuretointernal discovery(prevention + appraisal + internal failure). Internal discovery cost per defect:€200 + €400 + €150 = €750. External failure cost per defect:€2,500. Net saving per defect moved inside:€2,500 # €750 = €1,750. For50defects:€1,750 × 50 = €87,500#answer: €87,500.The syllabus directs test managers to articulate testing' s value by quantifyingavoided external failure costsagainstprevention, detection, and internal failure costs, supporting investment decisions and demonstrating ROI for testing initiatives (Chapter: Test Management in the Organization - economics/cost of quality; business case and benefit evaluation).
TM3 Exam Question 9
You are a test manager developing a master test plan. As part of the master test plan, you are defining exit criteria for the various test levels. Which of the following exit criteria would be most appropriate and SMART for component testing, and which one would be most appropriate and SMART for system testing? i. 95% of the tests prepared are executed successfully ii. All test cases have been run iii. 80% decision coverage for all tests run iv. At least 30 defects have been found v. At least two weeks of test execution vi. No more open defects
Correct Answer: C
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus: The syllabus emphasizesSMART exit criteriatailored to the test level: Forcomponent testing, structural coverage metrics (e.g.,decision coverage) are appropriate and measurable at code level, makingiii (80% decision coverage)suitable and SMART. References: ISTQB CTAL-TM v3.0 Syllabus-Chapter 3 (Test Planning: defining level-appropriate and measurable entry/exit criteria; use of structural coverage for lower levels and outcome/behavior criteria for higher levels).
TM3 Exam Question 10
The diagram below shows an incomplete defect management process, where three states (states X, Y and Z) have yet to be named appropriately. Which of the following labels would correctly complete the process?
Correct Answer: A
According to theISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus (Chapter 2: Test Management in the Organization), thedefect management processdefines how defects are handled from discovery to closure, ensuring traceability and communication between testing and development. "The defect management process defines the states a defect may have during its lifetime, including identification, evaluation, correction, re-testing (confirmation testing), and closure." (ISTQB CTAL-TM v3.0 Syllabus, Chapter 2 - Defect Management Process) In the standard ISTQB defect workflow: Afterevaluation, a defect can either be: Rejected(e.g., not a defect, duplicate, or out of scope), or Accepted(X) - meaning it is confirmed as a valid defect and will be corrected. Once accepted, the defect isplannedfor correction andfixedby development. After being fixed, it must betested (Y)- also referred to asconfirmation testingorretesting. Some evaluated defects may bedeferred (Z)- postponed for future releases. Thus, the correct states are: X = Accepted(defect confirmed as valid and correction planned) Y = Tested(confirmation testing after the fix) Z = Deferred(postponed correction) This sequence aligns directly with the ISTQB-defineddefect management lifecycle, which includes transitions betweenopen,evaluated,accepted (planned/fixed/tested), andclosed, as well as possiblerejectedordeferredbranches. References (from ISTQB Certified Tester Advanced Level - Test Manager v3.0 Syllabus): Chapter 2: Test Management in the Organization Section:Defect Management Process Describes thedefect states, includingopen, evaluated, accepted, planned, fixed, tested (retested), closed, and alternate states such asrejectedordeferred.
