What is the primary focus of 'white-box testing'?

The primary focus of white-box testing is to examine the internal code structure of the application under test. This testing method involves looking at the internal workings of the software, including the logic, algorithms, and code paths. By doing so, testers can ensure that the internal operations behave as expected, allowing for a more thorough assessment of the application’s functionality and performance.

White-box testing enables testers to identify potential vulnerabilities, optimize code, and verify that the various components interact correctly at the code level. This approach often involves techniques such as code coverage analysis, control flow testing, and path testing.

In contrast, the other options focus on aspects that do not align with the intent of white-box testing. For example, analyzing user satisfaction and assessing external customer interactions pertain more to user experience and usability testing rather than the internal mechanics of the software. Verifying requirement specifications is closely related to black-box testing, where the focus is on ensuring that the software meets the specified requirements without any regard to how those requirements are implemented internally.