CTFL2018 CTFL_Syll2018 Reddit Questions

Static analysis is a technique to find defects in software source code and software models, performed without executing code. Static analysis can be done manually or automatically using tools that examine the code or design of a software system without running it. Static analysis can help identify and prevent defects, measure complexity, check compliance, or improve quality.

The other statements are not correct definitions of static analysis because they describe different concepts related to testing. For example:

• A. The decision between using white or black box test techniques: This statement describes a test strategy, which is an approach or method for designing and executing test cases based on various factors, such as scope, objectives, risks, resources, etc.
• B. Executing software to validate the most common path through the code: This statement describes dynamic testing, which is a technique to find defects in software by executing it under various conditions and inputs and comparing the actual results with the expected results.
• D. It is a testing technique used during system testing: This statement describes a test level, which is a group of test activities that are organized and managed together based on some criteria, such as objectives, scope, target audience, etc.

You can find more information about static analysis in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], Chapter 6, Section 6.3.

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.

State transition testing is a technique that uses state transition diagrams as a test basis to derive test cases2. A state transition diagram shows the states of a system and the transitions between them triggered by events or conditions2. A test case can cover one or more state transitions, depending on the test objective and coverage criterion2. In this question, the test cases (i) and (ii) cover different sets of state transitions, as shown below:

Test Case

State Transitions

(i) X-Z-V-W

S1 – S2 – S3 – S4 – S2

(ii) W-Y-U-U

S4 – S2 – S4 – S4 – S4

 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.