Selenium provides a tool named WebDriver, which allows testers to write scripts that can automate browser interactions. WebDriver provides a simple API to interact with browsers, making it easier for testers to create automation scripts for web applications without having to know intricate browser details.

Functional testing aims to validate the app's features by ensuring they function according to specified requirements. It verifies each function of the software application by feeding them input and examining the output.

Disabling the service is the immediate action to consider when an unauthorized service is running on an open port. This will prevent potential exploitation while the situation is further assessed. Running a malware scan is important, but the immediate threat is mitigated by stopping the service.

Cyclomatic complexity, introduced by Thomas McCabe, quantifies the complexity of a program by calculating the number of linearly independent paths through the source code. A higher cyclomatic value indicates a complex program with many branches, which may require more extensive testing to ensure each path is evaluated. It aids testers in assessing risks associated with the intricate logic of the code.

The "Assigned" bug status signifies that the bug has been assigned to a developer and is currently being addressed. "Open" means the bug has been recognized but might not be attended to yet. "Closed" denotes that the bug has been resolved. "Verified" signifies that the tester has verified the fix.

While automated tests can efficiently handle repetitive tasks, manual testing is indispensable for exploratory testing (where testers actively explore the application to identify issues) and usability checks to ensure a user-friendly experience.

Usability Testing not only evaluates the ease of use of a product but also examines its overall user interface, ensuring there's consistency in design, clear error messaging, and providing meaningful feedback. This ensures a seamless, user-friendly experience for the end-user.

Beta Testing is a phase where the software is exposed to the real-world potential users before the final release. It's a type of User Acceptance Testing (UAT) where actual users use the software and provide direct feedback. This feedback can be related to functionality, usability, performance, or any other aspect of the software.

QTP stands for QuickTest Professional. However, it was later rebranded by Hewlett-Packard (HP) as "Unified Functional Testing" (UFT). UFT provides a comprehensive solution for functional and regression testing and is one of the most popular tools in the testing industry for automating GUI testing tasks.

The risk avoidance strategy involves taking actions to remove the threat or condition that represents the risk entirely, essentially ensuring that the risk event doesn't occur. This strategy is employed when risks are deemed too high and cannot be mitigated.

In the V-model, each development stage corresponds to a testing phase. As the development progresses downwards on the left side of the "V", testing activities are prepared. When development reaches integration and system levels, the testing phases commence upwards on the right side of the "V". This ensures that testing is integrated in parallel with development, unlike the Waterfall model where testing happens after the entire development phase.

In white-box testing, "coverage" refers to the amount or percentage of the codebase that has been tested. It provides an objective measure to ensure that most, if not all, paths, branches, statements, and conditions in the code have been exercised.