TM3 Dumps 2026 - New BCS TM3 Exam Questions
Free TM3 Braindumps Download Updated on Mar 22, 2026 with 53 Questions
NEW QUESTION # 26
You are a test manager in charge of integration, system, and user acceptance testing for a bank. You are working on a project to upgrade an existing ATM to allow customers to obtain cash advances from supported credit cards.
The system should allow cash advances from €20 to €500 (both inclusive) for all supported credit cards. The supported credit cards are American Express, VISA, Eurocard, and Mastercard. The system should be easy to use for all users, including new users. The organisation is currently in a transition to Agile and already well on its way.
In the test plan, the following items are listed under the heading"Items and features to be tested":
All supported credit cards
Language localisation
Valid and invalid advance
Usability
Response time
Which of the following topics would be most important for you to address in detail in the test plan?
- A. An approach to regression testing
- B. A set of logical test cases
- C. Detailed entry and exit criteria per test level
- D. A list of acceptance criteria for each of the user stories
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
According to theISTQB CTAL-TM v3.0 Syllabus, Chapter 3 - Test Planning, Monitoring, and Control, one of the main tasks oftest planningis todefine and document test completion criteria and test level entry criteriaas part of the test plan.
"The test plan shall include the entry and exit criteria for each test level, including the conditions that must be met to start and finish testing activities at that level." (ISTQB CTAL-TM v3.0 Syllabus, Chapter 3: Test Planning activities) Thetest planprovides the structure for managing multiple test levels such as integration, system, and user acceptance tests. Since this question context explicitly mentions severaltest levels, the most critical aspect to document in detail isthe entry and exit criteria per test level, ensuring clarity on when each test level starts and completes, and what constitutes sufficient testing for release or transition.
Why the other options are incorrect:
A). An approach to regression testing- While important, regression strategy typically belongs to thetest approachsection, not the detailed planning of multi-level testing criteria.
B). A list of acceptance criteria for each of the user stories- This belongs toAgile acceptance testdocumentation, not the formaltest planfor multiple test levels (integration, system, UAT).
D). A set of logical test cases- Test cases are outputs oftest design, not part of thetest plandocument.
References:
ISTQB Certified Tester Advanced Level - Test Manager Syllabus v3.0
Chapter 3: Test Planning, Monitoring, and Control
Section:Test Planning Tasks
Subsection:Define test completion criteria (exit criteria) and entry criteria for each test level Table of contents and body text referring to"items and features to be tested","entry and exit criteria", and
"content of the test plan".
NEW QUESTION # 27
A company that sells an established capture-replay execution tool is adding a test management tool. Same team, same technology, incremental development (V-model per increment), known first-year features; later features driven by customer demand.
Which two of the following factors are most likely to influence the estimation technique that would be selected in this scenario?
- A. Data availability
- B. Estimation error
- C. Time constraints
- D. Expert availability
- E. Knowledge in modelling
Answer: A,D
Explanation:
According to theISTQB Certified Tester Advanced Level - Test Manager v3.0 Syllabus (Chapter 3: Test Planning, Monitoring, and Control), the choice oftest estimation techniquedepends on several influencing factors, including data availability, expert availability, and knowledge of historical information or models.
"The selection of a suitable estimation approach (metrics-based or expert-based) depends on factors such as the availability of relevant historical data, the availability of experts with appropriate experience, the time available to perform estimation, and the knowledge of applicable models." (ISTQB CTAL-TM v3.0 Syllabus, Chapter 3 - Test Planning, Section: Test Estimation) Analysis for this scenario:
* The organization isadding a test management toolto anexisting productusing thesame team and technology- implyingavailability of previous project datafrom similar development work.#Data availability(B) is a significant factor, enabling the use ofmetrics-based estimation.
* Thesame experienced teamis working on the project, meaningdomain and technical expertsare available.#Expert availability(C) also influences estimation and may support anexpert-based estimationapproach for new, customer-driven increments.
Therefore, the combination ofdata availability (B)andexpert availability (C)most strongly influences the estimation technique to be applied in this scenario.
Why the Other Options Are Incorrect:
* A. Estimation error- This is a result of estimation, not a factor influencing the choice of estimation technique.
* D. Knowledge in modelling- While useful, modelling is not central to this specific context because data and experts are readily available.
* E. Time constraints- Not highlighted as a limiting factor in this scenario; estimation can be planned adequately given the context.
References (from ISTQB Certified Tester Advanced Level - Test Manager v3.0 Syllabus):
* Chapter 3: Test Planning, Monitoring, and Control
* Section:Test Estimation
* Lists influencing factors for selecting estimation techniques:availability of historical data, expert knowledge, applicable models, and time available for estimation.
NEW QUESTION # 28
Which of the following activities in the test process is considered to deliver a document which can be used as a major input for test process improvement?
- A. Test Monitoring
- B. Test Execution
- C. Test Completion
- D. Test Planning
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
In the ISTQB CTAL-TM v3.0 syllabus (Chapter:Testing Process, section onTest Completion), the Test Completion activity includes producing thetest summary report, capturinglessons learned, and finalizing
/archiving testware. Thetest summary report and lessons learned are specifically identified as key inputs to test process improvement, enabling organizations to refine their approach, improve efficiency, and address gaps revealed during the test effort. This makesTest Completionthe activity that delivers the document(s) most directly used for ongoingtest process improvement.
(Reference: CTAL-TM v3.0 Syllabus - Chapter "Testing Process", subsection "Test Completion":
responsibilities include creating the test summary report, collecting lessons learned, and providing input to process improvement.)
NEW QUESTION # 29
For which type of testing would a test manager be involved with establishing benchmarks?
- A. Functional Testing
- B. Testing Black-box
- C. Non-Functional Testing
- D. White-box Testing
Answer: C
Explanation:
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.)
NEW QUESTION # 30
Which of the following factors influences the risk impact?
- A. Frequency of use of the affected feature
- B. Geographically distributed teams
- C. Maturity of the development organisation
- D. Complexity of technology being used
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
In the syllabus,risk impactconcerns thepotential damage or lossif a failure occurs (business, user, financial, legal, or reputational).Frequency of use of the affected featureincreases theexposureand thus theimpactwhen defects occur, making optionBcorrect. By contrast,complexity of technology,organizational maturity, anddistributed teamsprimarily influencelikelihood(the chance of defects entering/escaping), not the impact dimension (CTAL-TM v3.0 Syllabus, Risk-Based Testing section explaining factors oflikelihood vs.
impactand examples of each).
NEW QUESTION # 31
Which of the following is not a key decision when defining a project test strategy?
- A. Selection of test types
- B. Selection of test tools
- C. Selection of test techniques
- D. Selection of test levels
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
In the AL Test Manager syllabus, defining the project test strategy/approach focuses onwhatto test andhowto test at a high level, which explicitly includes decisions such asthe selection of test levels,the selection of test types, andthe selection of test design techniquesas part of the approach definition and planning. Tool decisions are addressed undertest tools and automation planningand are not listed among the core strategy- defining decisions.
References: ISTQB CTAL-TM v3.0 Syllabus-Chapter 2 (Test Management in the Organization: policy
/strategy alignment and strategy content), Chapter 3 (Test Planning: test approach content including levels, types, techniques), and Chapter 6 (Test Tool and Automation: tool strategy and selection).
NEW QUESTION # 32
In multi-team environments with hybrid software development approaches, there are various challenges in the context of defect management, such as:
i. Alignment of defect attributes to be used
ii. Prioritisation of defects
iii. Alignment of the approach for defect fixes
Solutions to the above-mentioned challenges include:
- A. A = i, B = ii, C = iii
- B. A = i, B = ii, C = i
- C. Transparency of plans by sharing them between teams via dashboardsWhich solution is related to which challenge?
- D. Synchronisation between the defect management tools
- E. A = ii, B = i, C = iii
- F. A = i, B = iii, C = ii
- G. The product owner should be involved in the defect management meetings
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
ii. Prioritisation of defects # A. Product owner involvement: The PO (or equivalent business authority) ensuresbusiness-value/risk-based prioritizationis consistent across teams.
i. Alignment of defect attributes # B. Tool synchronization: Toalign fields/attributes/statuses, teams synchronize or harmonize defect management tools and schemas.
iii. Alignment of approach for fixes # C. Transparent shared dashboards:Shared plans/dashboardssupport coordination onhow/whenfixes are implemented across teams, improving consistency and visibility.This mapping reflects the syllabus coverage oforganization-level test management, multi-team governance, tool alignment, and cross-team transparency practices in hybrid/Agile environments (CTAL-TM v3.0, Chapter 2:
Test Management in the Organization; Chapter 5: defect management coordination and reporting).
NEW QUESTION # 33
Test control uses the information from test monitoring to provide guidance and take corrective action when required.
Which of the following is not a possible test control action?
- A. Checking the fulfilment of the exit criteria
- B. Adjusting the test schedule
- C. Re-prioritisation of test cases
- D. Adding new resources
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
The syllabus distinguishestest monitoring(collecting/assessing status information, e.g., progress vs plan, exit criteria status) fromtest control(takingcorrective actionsbased on monitoring).Control actionsincludere- prioritising tests,adjusting schedules, andadding resourcesto address variances and risks.Checking the fulfilment of exit criteriaismonitoringactivity (status assessment), not a control action.
(Reference: CTAL-TM v3.0 -Test Planning, Monitoring, and Control: differences between monitoring (status, metrics, exit criteria checks) and control (reprioritisation, rescheduling, resource adjustments, scope changes).)
NEW QUESTION # 34
In an Agile context, defects are often fixed without writing a formal defect report. However, there are some conditions where it is good practice to write a defect report, even in an Agile context.
When is a defect report typically not written in an Agile context?
- A. A defect that is found for a high-priority user story
- B. A defect that cannot be solved in the same iteration
- C. A defect that is blocking other iteration activities and cannot be immediately solved
- D. A defect that must be resolved by or in co-operation with other teams
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
Same rationale as Q35. In Agile,no formal defect reportis typically created when the team canfix the issue immediatelyand maintain flow (e.g., defect on a high-priority user story that is quickly addressed). Formal reports are encouraged whenblocking,spanning iterations, orrequiring cross-teamwork for visibility
/traceability. Refer to CTAL-TM v3.0, Chapter 5 on defect management and Agile reporting considerations.
NEW QUESTION # 35
You are involved in the selection of a test management tool and have decided to calculate the ROI for the two potential tools: TestMaker and ImproveIT.
TestMaker is priced at €15,000 with yearly maintenance costs of €1,500. Its traceability to requirements feature is strong and the defect management process can easily be customised to meet the needs of the organisation. Effort for test management activities is expected to decrease by 20%.
ImproveIT is priced at €20,000 with yearly maintenance costs of €2,500. Its traceability feature is also strong and has a high level of usability. It also has interesting options for adding extensions to its features in the future. Effort for test management activities is expected to decrease by 30%.
Based on the calculated ROI, which tool would you suggest?
- A. There is too little information to accurately calculate the ROIs
- B. ImproveIT
- C. TestMaker
- D. None of the tools, since they do not provide a positive ROI
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
InTest Tool and Automation, the syllabus states that determining thebusiness case/ROIfor a tool requires identifying and quantifyingall relevant costs(acquisition, maintenance,training,pilot/rollout,integration, customization) andbenefits(e.g.,effort reductionacross activities, quality and cycle-time gains), then comparing them over a defined period within the organization's context. A % effort reduction alone is insufficient without knowing thebaseline effort/cost, number of users, training/transition costs, and implementation scope. Therefore, ROI cannot be accurately computed with the given data.
(Reference: CTAL-TM v3.0 -Test Tool and Automation: tool selection and introduction; establishing a business case/ROI by quantifying costs and benefits; considering acquisition, maintenance, training, pilot, integration, process changes, and productivity gains.)
NEW QUESTION # 36
Your company is considering purchasing a test tool suite from a respectable vendor. Your manager has searched the internet for comparable products, but none of them meet his specific requirements. A tool demonstration has been arranged for next week and your team has been invited to attend. The tool suite consists of a test management tool, test execution tool, and a requirements management tool. There is a possibility of adding a performance testing tool at a later stage.
You have decided to attend the demo but raise some issues beforehand regarding expectations.
Which two issues from the options provided below should at least be raised?
- A. How will the implementation be organised?
- B. Which project will be selected to perform the tool pilot?
- C. What are the problems we are trying to address?
- D. Is customized training available?
- E. Do we have a set of tool requirements to validate the tool against?
Answer: C,E
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
The syllabus reminds test managers thattool introduction must be problem-drivenandrequirements-based.
Before (or alongside) demos, teams should clarify:
Athebusiness/testing problemsand improvement goals the tool is meant to address (e.g., traceability, automation scale, reporting).
Baclear set of tool requirements/selection criteriato objectivelyassess the toolduring a demo or evaluation.
These two are theminimum critical questionsto ground any evaluation. WhileC,D, andEare important for later stages (rollout planning, piloting, and training), ISTQB stresses thatsuccessful adoption starts with defined needs and evaluation criteria, ensuring the demo and subsequent selection are aligned to real objectives.
Relevant syllabus areas:Test Tool and Automation-Tool selection and introduction(identify problems
/opportunities, define requirements and success criteria, evaluate, then plan pilot/rollout/training).
NEW QUESTION # 37
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 come up with 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?
- A. €87,500
- B. €62,500
- C. €72,500
- D. €92,500
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
Per the syllabus, when building abusiness caseusing thecost of qualitymodel, compare theavoided external failure costswith thesum of relevant pre-release costs(prevention, detection/appraisal, and internal failure). For
50 expected defects found in testing:
Avoided external failure cost= 50 × €2,500 =€125,000
Pre-release costsper defect = €200 (prevention) + €400 (detection) + €150 (internal failure) =€750 Total pre-release costs= 50 × €750 =€37,500 Net benefit (cost-benefit)= €125,000 # €37,500 =€87,500 This computation follows the syllabus' guidance to quantify bothcosts(prevention, detection, internal failure) andbenefits(external failures avoided) to demonstrate the economic value of testing.
NEW QUESTION # 38
Study the following characteristics:
Avoid re-inventing the wheel
Pool on experiences from earlier projects
They prompt thought in areas that are sometimes forgotten
Often used when compliance to specific standards is relevant
To which risk identification technique do these characteristics relate?
- A. Risk Workshops
- B. Brainstorming
- C. Checklists
- D. Retrospectives
Answer: C
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
In the CTAL-TM v3.0 syllabus (Chapter on Risk-Based Testing), checklists are described as a reusable aid for identifying risks based on prior knowledge and experience. They help ensure important areas are not overlooked and are frequently used in contexts where compliance with standards is required. These characteristics match the question's bullets exactly (re-use/experience, prompting memory of commonly missed areas, and standards alignment).
Reference: ISTQB CTAL-TM v3.0 Syllabus, Chapter 4 (Risk-Based Testing) - section describingrisk identification techniquesincludingchecklists(purpose, reuse of prior experience, prompting thorough coverage, applicability for standards/compliance).
NEW QUESTION # 39
Which of the following statements about test management activities for an iterative development model is false?
- A. Roles are integrated; facilitator or coach typically replace the traditional test manager.
- B. Reporting is done at project milestones.
- C. The test approach is embedded within iterations, with a focus on adaptability and feedback.
- D. With testware the focus is on acceptance criteria and definition of done. The level of documentation is minimal.
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
In iterative/Agile contexts (Chapter:Test Management in the Organization), the syllabus emphasizes:
A: Testware tends to be lean; focus is onacceptance criteriaand theDefinition of Done; documentation is oftenminimalbut sufficient.
B: Thetest approach is integrated within iterations, emphasizingadaptability,continuous feedback, and close collaboration.
D: Traditional, centralized "test manager" roles are oftenevolved or distributed; responsibilities may be shared across the team, with afacilitator/coach (e.g., Scrum Master/Agile coach)supporting quality practices.
Cisfalsebecause in iterative modelsreporting is continuous and occurs every iteration (e.g., sprint reviews, daily information radiators), not only at traditionalproject milestonestypical of sequential models.(Reference:
CTAL-TM v3.0 Syllabus - Chapter "Test Management in the Organization", sections on Agile/iterative test management, roles, minimal documentation, and iterative reporting.)
NEW QUESTION # 40
You are working as a test manager at a company that develops software applications for the mobile domain.
The organisation has recently been assessed against TMMi. This assessment showed that the company is a TMMi level 1 organisation. The projects use the V-model lifecycle and an independent test team exists. The test team consists of both experienced and novice testers. The team has not yet been formally trained in testing, but an ISTQB Foundation course is scheduled to take place in two months.
In your role as a test manager working in the independent test team, you have recently performed a risk assessment for a mobile software application to be developed. You want the features that have been identified as major risks to be tested more thoroughly.
Which test practice would you propose to mitigate the identified major product risks?
- A. Create pairs of developers and testers to test the features with the highest risk levels together
- B. Assign the most experienced testers to test the features with the highest risk levels
- C. Use test design techniques such as equivalence partitioning and decision table testing
- D. Start a test improvement project to achieve TMMi level 2
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
The syllabus advises thatrisk mitigationincludes allocatingstronger capability and more efforttohigh-riskareas (e.g., by assigningmore experienced testersand more intensive testing to those features). In alow-maturity (TMMi level 1)context withnovice testers not yet trained, immediately deployingexperienced testersto high- risk items is the most practical and effective step to achievedeeper, more reliable testing.
Option B would be beneficial, but without formal training yet, immediate effectiveness is uncertain.
Option C is a longer-term improvement initiative, not a direct immediate mitigation for the current project risks.
Reference: ISTQB CTAL-TM v3.0 Syllabus, Chapter 4 (Risk-Based Testing) onallocating test effort and expertise according to product risk; Chapter 3 (Test Planning) onresourcing high-risk areasfirst.
NEW QUESTION # 41
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?
- A. X: Accepted, Y: Reviewed, Z: Duplicate.
- B. X: In Progress, Y: Verified, Z: Terminated.
- C. X: Accepted, Y: Tested, Z: Deferred.
- D. X: Approved, Y: Reviewed, Z: Deferred.
Answer: C
Explanation:
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.
NEW QUESTION # 42
You have been contracted to manage the user acceptance testing of a new reservation system for a travel agency. The reservation system is being developed by a third party. Detailed specifications are available, and an estimate of the total development effort exists. The system will be delivered in four agreed increments.
Which of the following estimation techniques would be most appropriate to use in this context?
- A. Wide-band Delphi
- B. Extrapolation
- C. Planning poker
- D. Estimation based on ratios
Answer: D
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
The syllabus describesratio-based estimation(e.g., estimating test effort as a proportion of known or estimated development effort) as appropriate when reliable development-effort data or estimates and clear scope are available. Here, detailed specifications exist, overall development effort is estimated, and increments are defined-conditions well-suited to ratio-based estimation.
Extrapolationrequires comparable historical test data for this context.
Wide-band Delphiis useful when data is scarce and expert consensus is needed.
Planning pokeris typically used by Agile development teams to size user stories, not for contracting UAT with a third party.
NEW QUESTION # 43
The following defect management process is in use at a company... What is the most important recommendation you would make for the defect report template in this process?
- A. Add a lifecycle phase field to document when the defect is found
- B. Add a priority field to show how quickly it needs fixing
- C. Automate the incident numbering
- D. Add a classification field for the type of incident
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
For effectivedefect management and control, the report needs information that supportsprioritization and scheduling of fixes. The syllabus emphasizes fields such aspriority/severity, status, environment, and reproducibility to supportplanning, monitoring, and controldecisions. In the described process, addingpriorityis most critical to drivetimely assignment and fixing order(Chapter 5: Test Monitoring, Control, and Reporting - defect reporting to support control; Chapter 3: Test Planning - using priorities to allocate effort).
NEW QUESTION # 44
You are a process improver and have decided to use the data from the defect management system to identify and drive improvement actions... Which of the following options could have been identified as missing from the defect reports to be used for process improvement?
- A. The software lifecycle phase in which the defect was detected
- B. The status of the defect
- C. The priority to fix the problem
- D. Steps to reproduce the failure, along with the actual and expected results
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
Forprocess improvement and root-cause analysis, the syllabus highlights the value ofdefect origin and detection phase datato evaluatewhere defects are injected and where they are detected, calculate removal effectiveness, and focus improvements (e.g., earlier-phase prevention or reviews). Thelifecycle phase detectedenables meaningful analysis ofphase containment, trends, and improvement targets; the other fields are useful operationally but less pivotal fororganizational/process improvement analytics(Chapter 2: Test Management in the Organization - improvement approaches using defect data; Chapter 5: Reporting and analysis of defect trends).
NEW QUESTION # 45
Which of the following is a generic good practice in adopting and rolling out of a new test tool?
- A. Define guidelines for the use of the tool
- B. Consider the pros and cons of the various licensing models
- C. Understand how the tool can technically and organisationally be integrated into the software development lifecycle
- D. Identify opportunities for process improvement supported by the tool
Answer: A
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
The syllabus onTest Tool and Automationlistsgood practices for tool adoption and rollout, including establishingusage guidelines/standardsso teams apply the tool consistently, effectively, and in alignment with the defined process and objectives. WhileBandCare also sensible activities in a broader adoption plan, thegeneric, universally applicable good practiceemphasized in ISTQB materials is todefine and communicate clear guidelines for tool use(roles, workflows, conventions, quality gates), backed by training and a measured rollout.D(licensing considerations) is a procurement detail and not a core "generic" practice highlighted for successful rollout.
Relevant syllabus areas:Test Tool and Automation-Tool selection, introduction, and successful deployment practices(guidelines, training, pilot, measured rollout, integration with process).
NEW QUESTION # 46
Which of the following tools help to understand which part of the test object has been exercised by testing?
- A. Requirements management tool
- B. Code coverage tool
- C. Test execution tool
- D. Static analysis tool
Answer: B
Explanation:
Comprehensive and Detailed Explanation From Exact Extract of ISTQB Certified Tester Advanced Level - Test Manager v3.0 syllabus:
UnderTest Tool and Automation, the syllabus explains thatcoverage tools(often calledcode coverage tools) measurewhich parts of the code or structure(e.g., statements, branches, conditions) have beenexecuted by tests. This directly answers the question about "which part of the test object has been exercised." Amanages requirements and traceability, not execution coverage.
Bexecutes tests but typically does not measure structural coverage of the code by itself.
Canalyzes code without executing it; it identifies defects or coding standard violations, not runtime coverage.
Relevant syllabus areas:Test Tool and Automation-Coverage measurement tools(structural coverage for assessing extent of code exercised by testing).
NEW QUESTION # 47
......
BCS TM3 Exam Practice Test Questions: https://actual4test.torrentvce.com/TM3-valid-vce-collection.html