ISTQB CTFL-2018 Practice Test - Questions Answers, Page 36

The correct answer is C, as it is an example of a project risk.A project risk is a risk that affects the management and control of the testing project, such as planning, budget, schedule, resources, quality, or scope1.Team members' skills may not be sufficient for the assigned work is a project risk, as it affects the quality and efficiency of the testing activities1. Option A is incorrect, as it is an example of a product risk.A product risk is a risk that affects the quality of the software product under test, such as functionality, reliability, usability, security, or performance1.A system architecture may not support some non-functional requirements is a product risk, as it affects the reliability and performance of the software product1. Option B is incorrect, as it is an example of a defect.A defect is a flaw in the software product that causes it to produce incorrect or unexpected results or behavior1.A computation is not always performed correctly in some situations is a defect, as it causes the software product to produce incorrect results1. Option D is incorrect, as it is an example of a defect.A defect is a flaw in the software product that causes it to produce incorrect or unexpected results or behavior1.Specific modules do not adequately meet their intended functions according to the user is a defect, as it causes the software product to produce unexpected behavior1.

Reference:1, Section 2.8

The correct answer is A, as it includes the items that would be most useful to include in the defect report.A defect report is a document that describes and records any anomaly found during testing2. A defect report typically includes information such as:

The expected results

The actual results

A description of the defect in order to reproduce, including screenshots and database dumps

These items are useful to include in the defect report, as they help the developers to understand and fix the defect2. Option B is incorrect, as it includes an item that would not be useful to include in the defect report.The urgency and priority to fix this is not useful to include in the defect report, as it is determined by the test manager or other stakeholders based on various factors such as severity, impact, risk, and business value2. Option C is incorrect, as it omits an item that would be useful to include in the defect report.The actual results are useful to include in the defect report, as they show what happened when the defect occurred2. Option D is incorrect, as it omits two items that would be useful to include in the defect report.The expected results and a description of the defect in order to reproduce are useful to include in the defect report, as they show what should have happened and how to replicate the defect2.

Reference:2, Section 2.9

Maintenance testing is important after migration, retirement or enhancement of an existing system. defines maintenance testing as follows:

Maintenance testing is a type of software testing that occurs after changes have been made to a system in order to ensure that no new defects have been introduced and that the system still meets its original requirements and specifications.

Regression testing (A) is important after any change in the system that may affect existing functionality. Operational acceptance testing (B) is important before deploying a system into production environment. System testing is important after integrating all components of a system into a complete system.

A main objective of a pilot project for introducing a new test tool into an organization is to learn more detail about the tool and how it fits with existing processes. states this as follows:

A pilot project should be conducted before introducing a new test tool into an organization in order to learn more about how to use it effectively and efficiently in your context and how it will interact with other tools and processes.

A pilot project is not meant to immediately save cost for current projects in your organisation (A), as it may require additional resources and time to set up and evaluate the tool. A pilot project is not meant to show competitors that your organisation is improving its test process (B), as it is an internal activity that may not be visible or relevant to external parties. A pilot project is not meant to motivate the test team and make testers feel valued , as it may cause resistance or frustration if the tool is not suitable or easy to use.

100% branch coverage means 100% statement coverage, but not vice-versa. Branch coverage is a stronger criterion than statement coverage, as it requires that every possible outcome of each decision point is executed at least once.Statement coverage only requires that every executable statement is executed at least once1explains this as follows:

Branch Coverage (also known as Decision Coverage) measures which possible branches in flow control structures are followed. Branch Coverage is a testing method, which aims to ensure that each one of the possible branch from each decision point is executed at least once and thereby ensuring that all reachable code is executed.

Statement Coverage measures the number of statements in the source code that are executed during the test. Statement Coverage is a metric, which is used to calculate and measure the number of statements in the source code which have been executed during testing.

B, C, and D are false statements. 100% statement coverage does not mean 100% branch coverage (B), as there may be some branches that are not covered by the test cases. 100% branch coverage does not mean 100% statement coverage and vice-versa , as branch coverage implies statement coverage but not the other way around. It is possible to achieve 100% statement coverage (D), but it may not be feasible or cost-effective for some systems.

Test implementation and execution is the activity in the fundamental test process that includes test script generation.Test script generation is the process of creating executable test cases from test conditions and test data2defines this activity as follows:

Test implementation and execution has the following major tasks:

Develop and prioritize test cases, creating test data and writing test procedures.

Check test environment has been set up correctly.

Execute test cases, evaluate results and document deviations from expected results.

Use exit criteria to report on suitability of system under test.

Test closure activities (A) include finalizing and archiving test results, evaluating the test process, identifying areas for improvement, and celebrating achievements. Test analysis and design (B) include reviewing test basis, identifying test conditions, designing high-level test cases, and defining exit criteria. Test planning and control include defining test objectives, scope, strategy, resources, schedule, risks, and metrics.

Test analysis and design is the activity in the fundamental test process that includes identifying necessary test data.Test data are the inputs that are used to execute the test cases and verify the expected results2defines this activity as follows:

Test analysis and design has the following major tasks:

Reviewing the test basis (such as requirements, risk analysis reports, design documents or code).

Identifying test conditions based on analysis of test items, specifications, behavior and structure of the software.

Designing high-level test cases based on test conditions and designing techniques.

Evaluating testability of requirements and system under test.

Defining exit criteria.

Evaluating exit criteria and reporting (A) is part of the test closure activities, where the results of testing are evaluated against the defined objectives. Test implementation and execution (B) is where the test cases are executed using the identified test data and deviations from expected results are documented. Test planning and control is where the overall approach and resources for testing are defined and monitored.

The correct answer is A, as it explains a drawback of independent testing.Independent testing is a type of testing that is performed by a person or team that is not involved in the development of the software1.Independent testing can have many benefits, such as providing an objective view of the software quality, reducing conflicts of interest, and increasing the effectiveness and efficiency of testing1.However, independent testing can also have some drawbacks, such as being isolated from the rest of the development and project team1.This can lead to communication problems, lack of collaboration, and misunderstanding of requirements and expectations1. Option B is incorrect, as it does not explain a drawback of independent testing, but a benefit.Due to their differing backgrounds and perspectives, an independent test team may discover defects that the developers did not uncover1.This can improve the quality of the software and reduce the risk of failures in operation1. Option C is incorrect, as it does not explain a drawback of independent testing, but a strength.An independent test team may possess specializations in specific test types such as usability or security that enhance the overall effectiveness of the test team1.These test types may require specialized skills, tools, or environments that are not available to the developers or other testers1. Option D is incorrect, as it does not explain a drawback of independent testing, but a misconception.Having the business organization participate as an independent test team can benefit the overall testing effort since business participants can provide valuable feedback on the user requirements, expectations, and satisfaction1.However, business participants are often not trained nor experienced in testing, so they should not be the only source of independent testing1.They should be supported by professional testers who can apply appropriate test techniques and methods1.

Reference:1, Section 2.2

The correct answer is D, as it describes a task that is most likely to be performed by the tester.A tester is a person who performs testing activities such as planning, designing, executing, and evaluating tests2.Creating the detailed test execution schedule is one of these activities, as it involves defining the order and timing of test cases to be executed based on various factors such as dependencies, risks, priorities, and resources2. Option A is incorrect, as it describes a task that is most likely to be performed by the test manager.A test manager is a person who leads and manages testing activities such as establishing test policies and strategies, managing test teams and stakeholders, monitoring and controlling test progress and quality, and reporting on test results2.Developing a test strategy and test policy for the organization is one of these activities, as it involves defining the overall approach and objectives for testing at an organizational level2. Option B is incorrect, as it describes a task that is most likely to be performed by the test analyst.A test analyst is a person who supports testing activities such as analyzing requirements and risks, designing and prioritizing tests, evaluating test coverage and traceability, and reviewing work products2.Introducing suitable metrics for measuring test progress is one of these activities, as it involves defining and collecting quantitative data to monitor and control various aspects of testing such as efficiency, effectiveness, quality, and maturity2. Option C is incorrect, as it describes a task that is most likely to be performed by the test leader.A test leader is a person who coordinates testing activities such as planning and estimating tests, allocating tasks and resources, supervising test execution and evaluation, communicating with stakeholders, and resolving issues2.Promoting and advocating the test team within the organization is one of these activities, as it involves demonstrating the value and benefits of testing to other parties such as management, developers, customers, and users2.

Reference:2, Section 2.3