Load Testing is specifically designed to simulate a specific expected load on a system to determine how it behaves. For an e-commerce website expecting a surge in traffic, it's crucial to understand how the system will handle the increased number of users to ensure seamless shopping experiences.

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.

"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.

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.

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.

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.

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.

Modular scripting divides the test scripts into small, manageable modules or functions. These modules can then be reused across multiple test scripts. This approach not only promotes reusability but also simplifies maintenance. If a functionality changes, only the respective module needs to be updated, without affecting other scripts.

The Configuration Library is the official repository where all approved and finalized configuration documentation is stored. It ensures that there is a single source of truth, reducing confusion and inconsistencies that may arise from using outdated or unofficial documents.

GUI (Graphical User Interface) Testing primarily focuses on the software's visual elements, ensuring that they adhere to design specifications. This includes validating button placements, color schemes, layouts, navigation, and other graphical elements to ensure a user-friendly and functional interface.