What is primarily assessed through build verification tests?

Build verification tests are designed to quickly assess whether the most crucial functions of a software build are working correctly after a new build is created. This type of testing focuses primarily on the core functionality and stability of the build to ensure that it is at a level where further testing can be conducted safely.

The goal of these tests is to identify any major issues that could prevent further testing activities. For example, if a critical feature is not functioning as expected, it may halt the entire testing process until the issue is resolved. By concentrating on the core functionality and stability, build verification tests help maintain the software's reliability as it evolves through continuous integration and frequent updates.

While the other options touch on important aspects of software quality, they do not align with the primary purpose of build verification tests. For instance, security compliance and performance under heavy load are typically assessed in separate testing phases rather than in initial build verification. Similarly, integration with external systems is considered during later phases of testing when the software's interaction with other systems is evaluated. Thus, the focus of build verification tests remains on ensuring that the essential functionalities are intact and stable.