Changed CTFL_Syll2018 Exam Questions

Component testing is concerned with testing the smallest bodies of software, such as functions, classes, procedures, or modules. Component testing is also known as unit testing or module testing. Feature testing is a type of functional testing that focuses on verifying a specific feature or functionality of a system. Functional testing is a type of black-box testing that verifies that the system meets its functional requirements and specifications. Subsystem testing is a type of integration testing that verifies that a group of components work together as expected. References: ISTQB Certified Tester Foundation Level Syllabus 2018, Section 2.2

 According to the syllabus, there are two main approaches for estimating test effort: metrics-based and expert-based. The metrics-based approach uses metrics from previous similar projects or industry data to calculate the test effort based on the size and complexity of the software under test. The expert-based approach relies on the experience and judgment of the owners of the testing tasks or subject matter experts who provide their estimates based on their knowledge of the software under test. The answer B is correct because it accurately describes the expert-based approach. The other answers are incorrect because they either confuse the metrics-based and expert-based approaches or describe them incorrectly.

References: Certified Tester Foundation Level Syllabus, Section 2.3.1, page 24-25.

The attributes that best match each level of testing are as follows14:

• Component testing: Stubs and drivers are often used (I), as they simulate the behavior of missing or incomplete components.
• Integration testing: Testing for functional and non-functional characteristics (VI), as integration testing verifies that components interact correctly and meet their specified requirements.
• System testing: The test environment should correspond to the production environment (II), as system testing evaluates the system’s compliance with its specified requirements under realistic conditions.
• Acceptance testing: Testing can be based on use cases (IV), as acceptance testing validates that the system meets the user’s needs and expectations

In a Scrum development life cycle model, regression testing is an increasingly important activity as the project progresses. Scrum is an agile framework that follows an iterative and incremental approach to software development, where the software is delivered in small units called sprints. Regression testing is a type of testing that verifies that previously tested software still performs as expected after changes or modifications. Regression testing is essential in Scrum, as new features or functionalities are added or modified in each sprint, which can introduce new defects or affect existing ones. Therefore, regression testing should be performed at the end of each sprint, as well as before releasing the software, to ensure that the software meets the quality standards and user expectations.

References: Certified Tester Foundation Level Syllabus, Section 5.3.2