The Test Designer is responsible for creating detailed test cases based on system requirements. They closely collaborate with business analysts, developers, and stakeholders to understand the functionality and behavior of the application to be tested.

Error Guessing is a technique where testers use their experience to guess the problematic areas of an application and create tests specifically for those areas. In this scenario, the tester's discovery of an uncommon defect based on past experiences aligns with the principles of Error Guessing.

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.

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.

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.

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.

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.

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.