CTFL_Syll2018 Dumps With Exact Questions and Answers

For the code fragment given below, one test case is required for statement coverage and two test cases are required for branch coverage. Statement coverage requires that every executable statement in the code is executed at least once. Branch coverage requires that every possible outcome of each decision point in the code is executed at least once. The following table shows how to achieve statement and branch coverage for the code fragment:

Test Case

Input

Output

Statement Coverage

Branch Coverage

1

x = 3

y = 9

S1, S2, S3

T1 = true

2

x = 5

y = 25

S1, S2

T1 = false

As shown in the table, test case 1 covers all three statements (S1, S2, S3) in the code fragment, achieving 100% statement coverage. Test case 2 covers only two statements (S1, S2) in the code fragment, but it exercises a different outcome of the decision point T1 (if x < 4), achieving 100% branch coverage.

Integration testing is the process of testing the interactions between different components or subsystems of a system. It has the following characteristics:

• It can be done in an incremental manner, meaning that components or subsystems are integrated and tested one by one until the whole system is integrated and tested.
• It is usually done before system testing, which is the process of testing the system as a whole against its requirements and specifications.
• It includes functional tests, which are tests that verify the functionality and behavior of the system or its components.
• It includes non-functional tests, which are tests that verify the quality attributes of the system or its components, such as performance, reliability, security, etc.

Therefore, statements I, III, and IV are correct.

References: Certified Tester Foundation Level Syllabus, Section 5.1.2 and 5.2.2

According to the syllabus, use case testing is a technique that tests the functionality of a system using scenarios based on use cases. A use case is a description of how an actor interacts with a system to achieve a goal. A use case defines the expected behaviour and possible variations of the system under test. The answer A is correct because test cases are designed to exercise the defined behaviours of the use case and its variations. The other answers are incorrect because they are not true statements about use case testing. There can be multiple test cases for each use case, depending on the complexity and variations of the use case. Test cases can be derived from other sources besides activity diagrams, such as textual descriptions or flow charts. It is possible to measure use case test coverage by comparing the number of executed test cases with the number of defined test cases for each use case.

References: Certified Tester Foundation Level Syllabus, Section 4.5.1, page 49-50.