CTFL_Syll2018 Exam Dumps and Practice Questions

Metrics are quantitative measures that can be used to monitor and control various aspects of software testing processes and products1.Metrics can be used to monitor progress along with test preparation and execution by providing information about the status of testing activities, such as test planning, test design, test execution, test evaluation, defect management, etc1. Among the options given in this question, only C is a suitable metric for monitoring progress along with test preparation and execution.The failure rate in testing already completed is a metric that measures how many tests have failed out of the total number of tests executed1.This metric can indicate the quality of the software product under test and the effectiveness of the test cases1.It can also help to identify areas that need more attention or improvement in testing1. Therefore, this metric can be used to monitor progress along with test preparation and execution.

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

The correct answer is D, as DT1 and DT4 would achieve full coverage of the full decision table when combined with the test cases that have already been generated for rules 1 and 4.Decision table testing is a black-box test technique that uses a table to show combinations of inputs and their associated outputs1. In this case, the inputs are the account type, the amount entered, and the expected result. The outputs are the actions taken by the ATM system. The decision table has eight rules, each corresponding to a possible combination of inputs and outputs. The test cases that have already been generated for rules 1 and 4 are:

TC1: Account = Checking, Amount = $600, Expected Result = Process the transaction

TC4: Account = Savings, Amount = Not entered, Expected Result = Generate an error message

The additional test cases are:

DT1: Account = Checking, Amount = Not entered, Expected Result = Generate an error message

DT2: Account = Savings, Amount = $100, Expected Result = Process the transaction

DT3: Account = Checking, Amount = $100, Expected Result = Process the transaction

DT4: Account = Savings, Amount = $600, Expected Result = Generate an error message

To achieve full coverage of the full decision table, two more test cases are needed that cover the remaining six rules. DT1 and DT4 cover these rules, as shown in the table below:

Therefore, option D is the correct answer.Options A, B, and C are incorrect, as they do not cover all the rules in the decision table. Reference:1, Section 4.2.5

A test condition is an item or event of a component or system that can be verified by one or more test cases. A test condition can be derived from various sources of information, such as requirements, specifications, design documents, use cases, user stories, etc. A test condition can also be based on various aspects of a component or system, such as functionality, usability, performance, reliability, security, etc.

The other statements are not true about test conditions because they describe different concepts related to testing. For example:

B: The grouping of a composite set of test cases which, when tested as a whole, reveal a positive or negative result: This statement describes a test suite, which is a collection of test cases that are intended to be executed together to achieve a specific test objective or goal.

C: A testable component derived from business requirements: This statement describes a test basis, which is the source of information or data that provides the basis for designing and executing test cases.

D: Applies to software testing only: This statement is false because test conditions can apply to any type of testing, not just software testing. Test conditions can also be used for testing hardware, systems, processes, etc.

You can find more information about test conditions in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], Chapter 4, Section 4.1.

Functional testing to test security at the system level, load testing at the system level to ensure the system availability is acceptable, regression testing at all levels, structure based testing at the component level only are the test types that will be required during the development1. A bank is developing a new service that will be delivered via the web. The user interactions are defined as a set of use cases and the service is designed to be available continuously 24/7. In view of the challenging characteristics of the service, the test manager has decided that the code should be thoroughly tested at component level. Therefore, the following test types will be required during the development:

Functional testing to test security at the system level: This type of testing verifies that the software product performs its intended functions according to the user requirements and expectations1.Security is one of the functional aspects that needs to be tested at the system level, as it ensures that the software product protects itself from unauthorized access or harm1.

Load testing at the system level to ensure the system availability is acceptable: This type of testing verifies that the software product can handle the expected or peak load of users or transactions without degrading its performance or functionality1.Availability is one of the quality attributes that needs to be tested at the system level, as it measures how well the software product performs its intended functions under specified conditions without interruption or failure1.

Regression testing at all levels: This type of testing verifies that previously tested software still performs correctly after changes or defect corrections1.Regression testing is required at all levels of testing, as changes or defect corrections can introduce new defects or affect existing functionality1.

Structure based testing at the component level only: This type of testing uses the structure or logic of the source code as a test basis to derive test cases and measure test coverage1.Structure based testing is required at the component level only, as the test manager has decided that the code should be thoroughly tested at component level to ensure its quality and reliability1.