CTFL_Syll2018 Exam Dumps : ISTQB Certified Tester Foundation Level (Syllabus 2018)

Testing support tools are software tools that assist testers in performing testing activities, such as test management, test design, test execution, test evaluation, and defect management1. According to the ISTQB syllabus, some typical targets of testing support tools are to automate activities that require significant resources when done manually, automate activities that cannot be executed manually, and automate repetitive tasks1. Automating repetitive inspections is not a typical target of testing support tools, as inspections are static testing techniques that involve human review and analysis of software artifacts1.

The fundamental test process activity where the sufficiency of testing and resulting information are assessed is Evaluating exit criteria and reporting. This activity involves checking whether the test objectives have been met and whether there are any unresolved issues or risks that could affect the release or deployment decision. This activity also involves preparing and communicating a test summary report that summarizes the test activities and results and provides recommendations and feedback for improvement. You can find more information about Evaluating exit criteria and reporting in [A Study Guide to the ISTQB® Foundation Level 2018 Syllabus], Chapter 3, Section 3.5.

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