Feature flags or toggles are utilized in Continuous Integration primarily to progressively release new features to a subset of users or environments. This means that a feature can be developed and integrated into the main codebase but can remain hidden to users until it's ready for release. It provides developers with the flexibility to test new functionalities without affecting all users and roll back quickly if issues arise.

While automated testing provides speed and repeatability, it's less flexible when dealing with frequently changing interfaces. In situations where the application interface is evolving rapidly, manual testing is more adaptable and can more effectively handle changes without the need for constant script updates.

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.

The "Resolved" state in the bug life cycle indicates that the defect or bug has been addressed and fixed by the development team. It's now awaiting confirmation by the testing team to ensure that the fix is valid and doesn't introduce new issues.

The term "WCAG" stands for "Web Content Accessibility Guidelines." These guidelines provide a series of recommendations for making web content more accessible to people with disabilities, ensuring inclusivity and equal access to web content for all users, regardless of their physical or cognitive abilities.

For applications where security is paramount, a Security Tester becomes indispensable. Their primary focus is to identify vulnerabilities, threats, and potential security breaches. They have specialized knowledge in areas like penetration testing, risk assessments, and security protocols, ensuring the application's resilience against potential attacks.

Automated tests often rely on specific element locators or paths in the user interface. When the UI frequently changes, these locators may become invalid or outdated, leading to test failures. Regular maintenance and updates to the automated tests are needed, which can be time-consuming and erode the benefits of automation.

The Test Plan document in the testing process provides a comprehensive view of the testing objectives, resources, schedule, and other critical aspects of testing. While other documents like the Requirement Specification or Test Case Document might include specific details, the Test Plan offers an overall blueprint for the entire testing phase.

A UI/UX Tester primarily focuses on the usability, accessibility, and overall user experience of an application. They evaluate the interface, navigation, graphics, and overall user interaction with the software to ensure a seamless and intuitive experience.

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.

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.

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.