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

Exploratory testing can replace black box techniques when testing time is very limited, because it is a type of experience-based technique that allows testers to design and execute tests based on their intuition, knowledge, and skills, without following a predefined test plan or test cases13. The other options are false statements about testing techniques.Option B is false, because test execution scheduling should give priority to specification-based or structure-based techniques, which are more systematic and objective than experience-based techniques13.Option C is false, because specification-based techniques cannot be used as a substitute for a poorly defined test basis, but rather require a clear and complete test basis to design effective test cases13.Option D is false, because experience-based techniques are not systematic and do not produce detailed test documentation, but rather rely on the tester's judgement and creativity

Functional and structural testing can both be applied at all test levels, from component testing to acceptance testing1.Functional testing verifies whether the software meets the specified requirements and user expectations, while structural testing verifies whether the software meets the specified design and code standards1.Both types of testing can be useful at any stage of the software development life cycle, depending on the test objectives and scope1. The other options are incorrect, because they limit the application of functional and structural testing to certain test levels only.

The predicted number of defects and the amount of rework required is the most likely factor to impact the amount of testing effort required, because it affects the quality and stability of the software under test1.Testing effort can increase if there are many defects in the software that need to be detected, reported, fixed, and re-tested1. The other options are not likely to impact the amount of testing effort required directly.Option B is related to the size and composition of the project team, but it does not determine how much testing effort is needed for the software itself1.Option C is related to the use of a project management tool to schedule tasks, but it does not affect how much testing effort is needed for each task1.Option D is related to the responsibilities for testers and developers being clearly defined, but it does not influence how much testing effort is needed for their respective tasks1.

To ensure that users can navigate to all fields on the screen does not reflect structural testing, but rather functional testing or usability testing1.Structural testing verifies whether the software meets the specified design and code standards by measuring aspects such as code coverage, complexity, or coupling1. The other options reflect structural testing at different levels of granularity.Option A reflects structural testing at the system level by testing all paths that users could take through the screen menu system1.Option B reflects structural testing at the component level by ensuring that 100% decision coverage is achieved for each system component1.Option C reflects structural testing at the component integration level by testing all branches of component calls within the application call graph

Using a keyword-driven testing approach to separate the actions and data from the tool's script is the best approach to improve the way test automation tools are being used in your company, because it allows for more flexibility, maintainability, and reusability of automated test scripts1.A keyword-driven testing approach uses keywords or commands to represent actions or data in the test scripts, which can be stored in external files or tables and accessed by the tool1. The other options are not good approaches to improve the way test automation tools are being used in your company.Option A is not a good approach, because selecting and automating scripts that test new functionality to find the most defects does not consider the suitability, feasibility, and cost-effectiveness of automation1.Option C is not a good approach, because ensuring that all data, inputs and actions are stored in the tool's script for ease of maintenance makes the test scripts more rigid, complex, and difficult to modify1.Option D is not a good approach, because keeping expected results separate from the automation tool to allow the testers to check the results reduces the efficiency and reliability of automation and increases the manual effort

TC1 - 23 total charges including buggy hire; TC2 - 16 total charge but no buggy allowed. This answer can be derived from the decision table by matching the conditions of each test case with the corresponding rules and actions. For TC1, the conditions are: Loyalty Card holder = Y, 18 Holes = Y, Buggy/Cart Request = Y. These conditions match Rule 1, which has the actions: Green Fee = 18, Buggy Hire = 5, Total Charge = 23. For TC2, the conditions are: Loyalty Card holder = N, 18 Holes = N, Buggy/Cart Request = Y.These conditions match Rule 3, which has the actions: Green Fee = 16, Buggy Hire = Not Allowed, Total Charge = 16

A variable has the wrong numeric value passed into it is the type of defect that would not be typically found by using a static analysis tool, because it is a logical or functional error that depends on the context and requirements of the software13.A static analysis tool can detect syntactic or structural errors in the code, such as missing declarations, undefined variables, unused variables, or unreachable code13. The other options represent such errors that can be typically found by using a static analysis tool.Option A is an error where a variable is defined but is then not used, which indicates a waste of memory or a possible logic flaw13.Option B is an error where a variable is used in a calculation before it is defined, which can cause unpredictable results or exceptions13.Option D is an error where a variable is used but not declared, which can cause compilation or runtime errors

Reviewing tests developed by others would not typically be performed by a tester, but rather by a test leader or a peer reviewer1.Reviewing tests developed by others is an activity that involves checking the quality and completeness of the test cases or procedures and providing feedback or suggestions for improvement1. The other options are tasks that would typically be performed by a tester.Option A is a task that would typically be performed by a tester, because it involves preparing and acquiring the test data that are needed for executing the test cases or procedures1.Option B is a task that would typically be performed by a tester, because it involves setting up and checking the test environment that supports the execution of the test cases or procedures1.Option C is a task that would typically be performed by a tester, because it involves writing test summary reports that document the results and outcomes of the test execution1.

.Logging the outcome of test execution and reporting bugs is an activity that is performed as part of the Test Implementation and Execution activity, because it involves recording and communicating any deviations from the expected results or behaviour of the software under test1.Test Implementation and Execution is the process of running the test cases or procedures on the software under test and comparing the actual results with the expected results1. The other options are not activities that are performed as part of the Test Implementation and Execution activity, but rather as part of other activities.Option B is an activity that is performed as part of the Test Analysis activity, because it involves evaluating the testability of the test basis and test objects to identify test conditions1.Option C is an activity that is performed as part of the Test Closure activity, because it involves assessing if the specified exit criteria should be changed to determine when to stop testing1.Option D is an activity that is performed as part of the Test Planning activity, because it involves selecting metrics for monitoring test execution and defect resolution to measure the progress and quality of testing1.