The primary difference between test planning and test strategy is their purpose and scope. While test planning is a document that outlines the specifics of the testing process for a particular project, test strategy provides an overarching approach to testing across multiple projects or for an entire organization.

A Code Review is a systematic examination of the application's source code. It's conducted to find vulnerabilities or bugs before the app is deployed. While tools like Selenium and JUnit focus on functional testing, and Wireshark on network analysis, only a thorough code review provides insights into code vulnerabilities.

Path testing is a white-box testing technique that ensures every path through the program is tested at least once. It is particularly focused on evaluating the program's internal logic paths to ensure all code branches and potential execution paths are tested.

The "risk matrix" is a tool that visualizes risks in a matrix format, based on their likelihood (or probability) on one axis and their impact on another. By categorizing risks in this manner, teams can easily prioritize which risks need immediate attention and which can be addressed later or monitored.

Alpha Testing is usually performed in a controlled environment and involves internal teams. This allows the organization to receive feedback in a quicker and more direct manner. Beta Testing, on the other hand, involves actual users but may introduce challenges in managing feedback and potential public relations issues.

Accessibility testing primarily aims to ensure that applications and websites are usable by people with disabilities like visual, auditory, cognitive, and motor impairments. While usability, compatibility, and performance are important, they are separate areas of testing. Accessibility testing focuses on ensuring equal access and inclusivity.

Regularly refactoring test cases is an essential practice when managing large-scale test suites. As the application under test evolves, some test cases may become redundant, outdated, or irrelevant. Refactoring ensures that the test suite remains lean, relevant, and more maintainable, thereby keeping its effectiveness over time.

"Heuristic Evaluation" is a usability inspection method where expert evaluators individually review an interface based on a list of recognized usability principles, known as heuristics. These evaluators identify usability problems in the design, allowing designers to rectify these issues for an improved user experience.

Exploratory Testing involves testers exploring the software without pre-defined test cases or a specific plan. It's a dynamic process where testers learn the application and simultaneously design and execute tests to find defects.

Regression Testing is the process of testing changes to applications to make sure that the older programming still works with the new changes. It's crucial when there are frequent code changes to ensure that new code doesn't negatively impact existing functionality.