ISTQB CTFL4 Practice Test - Questions Answers, Page 17

Test automation provides numerous benefits to software testing, and one of the key advantages is the reduction of repetitive manual work. This benefit is explicitly covered in the ISTQB Foundation Level Syllabus (v4.0).

Test automation allows testers to automate repetitive tasks such as regression testing, freeing up their time to focus on more complex and exploratory testing. This leads to improved efficiency and helps in avoiding human errors associated with repetitive tasks.

Option A: 'More subjective assessment' contradicts the benefit of automation as it focuses on objectivity.

Option C: 'Availability of the test automation tool vendor' is not a direct benefit of test automation, although vendor support can be valuable.

Option D: 'Negligible effort to maintain the test assets' is misleading as maintaining automated tests often requires effort and attention to changes in the system under test.

Therefore, the correct answer is B (ISTQB not-for-profit association) (ISTQB).

Certified Tester Foundation Level v4.0

ISTQB Foundation Level Syllabus 4.0 (2023)

Confirmation testing, also known as re-testing, is performed to verify that specific defects have been successfully fixed.

Option A: 'Testing due to the application of a new version of the interface' would typically involve regression testing, not confirmation testing.

Option B: 'Testing that fixes resolved the defects in the search function' fits the description of confirmation testing as it focuses on ensuring that specific issues have been addressed.

Option C: 'Testing if a system still works after update of an operating system' is an example of regression testing, as it checks the overall system behavior after an update.

Option D: 'Testing to ensure the adding of new functionalities haven't broken existing functions' is another example of re (ISTQB not-for-profit association) (Udemy) it checks for unintended consequences of new changes.

Therefore, the correct answer is B6source9source.

Certified Tester Foundation Level v4.0

ISTQB Foundation Level Syllabus 4.0 (2023)

Maintenance testing is triggered by changes such as bug fixes, enhancements, or environmental changes.

Option A: 'Completion of architecture of the bank system' is not a typical scenario for maintenance testing, as it describes a design phase rather than an operational change.

Option B: 'Release of the early draft of the low level project design of an IoT application' is again not suitable for maintenance testing, as it refers to the design phase.

Option C: 'Defect was found in a pre-released version of the customer service application' is closer but not quite accurate, as maintenance testing focuses on changes mad (ISTQB not-for-profit association)system is released.

Option D: 'Delivery of the hot fix to mobile operating system and ensuring that it still works' is the best example as it directly involves testing after a fix has been implemented.

Therefore, the correct answer is D6source.

Certified Tester Foundation Level v4.0

ISTQB Foundation Level Syllabus 4.0 (2023)

Static testing involves reviewing and inspecting the code, requirements, or design documents without executing the code. It can prevent defects, is effective early in the software development life cycle, and can help eliminate defects in user stories.

Option 1: 'It can prevent defects by manual examination of the functional specification' - This is a value of static testing.

Option 2: 'It is effective since it can be performed very early in the software development life cycle' - This is a value of static testing.

Option 3: 'It can detect the failures in the running application' - This is a v (ISTQB not-for-profit association)namic testing, not static testing.

Option 4: 'It can help eliminate defects in user stories' - This is a value of static testing.

Option 5: 'It can verify externally visible behaviors' - This is a value of dynamic testing, not static testing.

Therefore, the correct set of statements representing values only for static testing is 1, 2, 4, which corresponds to answer C6source.

Certified Tester Foundation Level v4.0

ISTQB Foundation Level Syllabus 4.0 (2023)

Test automation allows you to produce tests that are less subject to human errors, as they can execute predefined test scripts or test cases with consistent inputs, outputs, and expected results. Test automation can also reduce the manual effort and time required to execute repetitive or tedious tests, such as regression tests, performance tests, or data-driven tests. Test automation does not demonstrate the absence of defects, as it can only verify the expected behavior of the system under test, not the unexpected or unknown behavior. Test automation does not avoid performing exploratory testing, as exploratory testing is a valuable technique to discover new information, risks, or defects that are not covered by automated tests. Test automation does not increase test process efficiency by facilitating management of defects, as defect management is a separate activity that involves reporting, tracking, analyzing, and resolving defects, which may or may not be related to automated tests.Reference: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:

ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 3.3.1, Test Automation1

ISTQB Glossary of Testing Terms v4.0, Test Automation2

The support offered by a performance testing tool is often leveraged by testers to run load tests, which are tests that simulate a large number of concurrent users or transactions on the system under test, in order to measure its performance, reliability, and scalability. Performance testing tools can help testers to generate realistic workloads, monitor system behavior, collect and analyze performance metrics, and identify performance bottlenecks. The other statements are false, because:

A test data preparation tool is a tool that helps testers to create, manage, and manipulate test data, which are the inputs and outputs of test cases. Test data preparation tools are not directly related to running automated regression test suites, which are test suites that verify that the system still works as expected after changes or modifications. Regression test suites are usually executed by test execution tools, which are tools that can automatically run test cases and compare actual results with expected results.

A bug prediction tool is a tool that uses machine learning or statistical techniques to predict the likelihood of defects in a software system, based on various factors such as code complexity, code churn, code coverage, code smells, etc. Bug prediction tools are not used by testers to track the bugs they found, which are the actual defects that have been detected and reported during testing. Bugs are usually tracked by defect management tools, which are tools that help testers to record, monitor, analyze, and resolve defects.

A continuous integration tool is a tool that enables the integration of code changes from multiple developers into a shared repository, and the execution of automated builds and tests, in order to ensure the quality and consistency of the software system. Continuous integration tools are not used by testers to automatically generate test cases from a model, which are test cases that are derived from a representation of the system under test, such as a state diagram, a decision table, a use case, etc. Test cases can be automatically generated by test design tools, which are tools that support the implementation and maintenance of test cases, based on test design specifications or test models.Reference: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:

ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 3.4.1, Types of Test Tools

ISTQB Glossary of Testing Terms v4.0, Performance Testing Tool, Test Data Preparation Tool, Bug Prediction Tool, Continuous Integration Tool, Test Execution Tool, Defect Management Tool, Test Design Tool

Exercising at least one of the decision outcomes for all decisions within the code, ensures achieving full branch coverage, which is a test coverage criterion that requires that all branches in the control flow of the code are executed at least once by the test cases. A branch is a basic block of code that has a single entry point and a single exit point, and a decision is a point in the code where the control flow can take more than one direction, such as an if-then-else statement, a switch-case statement, a loop statement, etc. The decision outcomes are the possible paths that can be taken from a decision, such as the then branch or the else branch, the case branch or the default branch, the loop body or the loop exit, etc. The other statements are false, because:

The minimum number of test cases needed to achieve full branch coverage, is usually higher than that needed to achieve full statement coverage, which is a test coverage criterion that requires that all executable statements in the code are executed at least once by the test cases. This is because branch coverage is a stronger criterion than statement coverage, as it implies statement coverage, but not vice versa. For example, a single test case can achieve full statement coverage for an if-then-else statement, but two test cases are needed to achieve full branch coverage, as both the then branch and the else branch need to be exercised.

If full branch coverage has been achieved, then all unconditional branches within the code have not necessarily been exercised, as unconditional branches are branches that do not depend on any decision, and are always executed, such as a goto statement, a break statement, a return statement, etc. Unconditional branches are not part of the branch coverage criterion, as they do not represent different paths in the control flow of the code. However, they are part of the statement coverage criterion, as they are executable statements in the code.

If full branch coverage has been achieved, then all combinations of conditions in a decision table have not necessarily been exercised, as a decision table is a test design technique that represents the logical relationships between multiple conditions and their corresponding actions, in a tabular format. A decision table can have more combinations of conditions than the number of decision outcomes in the code, as each condition can have two or more possible values, such as true or false, yes or no, etc. For example, a decision table with four conditions can have 16 combinations of conditions, but the corresponding code may have only two decision outcomes, such as pass or fail. To exercise all combinations of conditions in a decision table, a stronger test coverage criterion is needed, such as condition combination coverage, which requires that all possible combinations of condition outcomes in the code are executed at least once by the test cases.Reference: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:

ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.3.1, Test Coverage Criteria Based on the Structure of the Software

ISTQB Glossary of Testing Terms v4.0, Branch Coverage, Statement Coverage, Branch, Decision, Decision Outcome, Unconditional Branch, Decision Table, Condition Combination Coverage

The minimum number of test cases needed to cover every unique sequence of up to 3 states/2 transitions starting in the ''Start'' state and ending in the ''End'' state is 4. This is because there are 4 unique sequences of up to 3 states/2 transitions starting in the ''Start'' state and ending in the ''End'' state:

Start -> Bet -> End

Start -> Deal -> End

Start -> 1st Deal -> End

Start -> 2nd Deal -> EndReference: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents.