Regular "Testing" in Continuous Integration ensures that the code changes made by developers are validated and verified to work as expected. This prevents defects from being introduced into the mainline and assures code quality in the final product.

Test Modularization refers to the process of breaking down test scripts into reusable modules or units. These modules can then be invoked or called by different test cases, ensuring that repetitive sequences or functionalities do not need to be scripted again, thus promoting reusability and reducing redundancy in the testing process.

The "sandwich" approach of integration testing merges both top-down and bottom-up methods. It allows simultaneous testing of the top and lower ends of software, ensuring quicker detection of interface errors throughout different levels of the application.

In the bug life cycle, after a bug has been fixed by the development team, it moves to the "Verified" stage. During this stage, testers retest the issue to confirm that the defect has indeed been resolved. If the fix is successful, it can then move to the "Closed" stage.

"Residual risk" refers to the risk that remains after all mitigation efforts have been applied. Even after implementing all the risk management strategies, there's often some level of risk that persists. It's crucial for organizations to understand this remaining risk and decide whether it's within acceptable limits or requires further action.

Path Testing is focused on testing all possible paths through the software, ensuring every single logical path has been covered. This approach makes sure that all the branches and decisions in the software are executed at least once, giving a comprehensive testing coverage to the logic embedded in the application.

The "Object Spy" feature is unique to QTP (Quick Test Professional). It allows testers to point and click on application objects to view their properties, making it easier to identify and understand the attributes of various application components. This aids in creating accurate and effective test scripts.

"Loop Testing" is a white-box testing technique that specifically focuses on validating all loops in the software application. This ensures that loops function as expected under all possible conditions and iterations.

In the error guessing technique, testers leverage their experience and intuition to predict where errors might be present. They often create an "Error Profile," which is a list or description of familiar errors or issues they've encountered in similar situations before. This helps streamline the testing process and targets specific areas that are prone to defects.

System testing is a level of testing where the complete system is tested as a whole. Thus, it should be prioritized when the complete system is ready for testing. This level of testing comes after integration testing and focuses on evaluating the system's compliance with the specified requirements. While unit tests evaluate individual components and integration tests ensure that those components interact well, system testing verifies that the entire system meets the desired specifications and functionalities.

Connectivity testing is essential for apps that may function differently under various network conditions. In this case, the app's performance on mobile data versus Wi-Fi can be assessed under different conditions to ensure consistent user experience. Other testing types, while valuable, may not directly diagnose this specific issue.

White-box testing, also known as Structural testing, emphasizes examining the internal structures and workings of an application. This is in contrast to black-box testing which focuses solely on the software's outputs in response to certain inputs, ignoring its internal mechanisms.