ISTQB CTFL-2018 Practice Test - Questions Answers, Page 10

It can be done without reference to the internal structure of the component or system. Black-box testing techniques are based on the external behavior and functionality of the system, not on its internal structure or code. Black-box testing techniques include equivalence partitioning, boundary value analysis, decision table testing, state transition testing, use case testing, etc. A detailed explanation of black-box testing techniques can be found inA Study Guide to the ISTQB Foundation Level 2018 Syllabus, pages 25-601.

Concerned with the behavior of a whole system/product as defined by the scope of a development project. System testing is a level of testing that evaluates the system as a whole against its requirements and specifications. System testing is performed after integration testing and before acceptance testing. System testing covers functional and non-functional aspects of the system, such as usability, performance, reliability, security, etc. A detailed explanation of system testing can be found inA Self-Study Guide For The ISTQB Foundation Exam Certified Tester Foundation Level (CTFL) 2018 Syllabus, pages 75-782.

Performance, Load, Stress. Performance testing is a type of non-functional testing that measures how well the system performs under various conditions, such as response time, throughput, resource utilization, etc. Load testing is a type of performance testing that simulates a high volume of user requests or transactions on the system and measures its behavior under normal and peak load conditions. Stress testing is a type of performance testing that simulates extreme or abnormal conditions on the system and measures its behavior under stress or overload conditions. These test types would help verify the requirements such as minimum number of enquiries per hour, availability, and response time under peak loads. A detailed explanation of performance, load, and stress testing can be found inSoftware Testing Foundations: A Study Guide for the Certified Tester Exam, pages 187-1913.

When an organization considers the use of testing tools, they should C. Perform analysis of the test process and then assess whether it can be supported through the introduction of tool support. Testing tools can provide many benefits to the test process, such as increased efficiency, effectiveness, consistency, quality, etc. However, testing tools also have some challenges and risks associated with them, such as cost, learning curve, compatibility, maintenance, etc. Therefore, before introducing any testing tool, an organization should analyze their current test process and identify their needs, goals, expectations, constraints, etc., and then evaluate whether a tool can support them or not. A detailed explanation of testing tools can be found inSoftware Testing Foundations: A Study Guide for the Certified Tester Exam, pages 193-1983.

Statement coverage is not a black box technique, because it requires knowledge of the internal structure of the code. Black box techniques are based on the external behavior and specification of the software, without looking at the code.Equivalence partitioning, state transition testing, and boundary value analysis are all examples of black box techniques12

Finding defects, gaining confidence about the level of quality and providing information, and preventing defects are all valid test objectives according to the ISTQB Foundation Level syllabus.Debugging the code is not a test objective, because debugging is the process of finding and fixing defects, which is done by developers, not testers3