Vulnerability Scanning is a systematic approach that uses specialized tools to identify, rank, and report potential vulnerabilities in a computer system or network. It provides an overview of the security flaws but doesn't necessarily exploit them like penetration testing.

JMeter is a popular open-source tool primarily used for performance testing. It allows testers to simulate multiple users and test how much load an app can handle, ensuring the app performs well under heavy usage. While it started for web applications, it is now used for mobile application load testing as well.

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.

Incremental Integration testing involves testing parts of a system sequentially as they're developed. In environments where multiple teams work on different components, this approach ensures that each new piece integrates smoothly with the existing parts, helping detect issues early and reducing integration risks.

A Walkthrough is a type of review where the author leads members of the review through the document based on their understanding. It's informal in nature and often relies on scenarios to provide the reviewers with a deeper understanding. The main goal is to gather feedback and achieve a common understanding.

Configuration Auditing is a critical aspect of Configuration Management. It involves the process of evaluating and examining the configurations to ensure that they align with the approved configuration documentation. Through this, unauthorized changes, discrepancies, or inconsistencies can be detected and addressed promptly.

Requirement-based Testing, as the name implies, involves designing test cases directly based on the system requirements. It ensures that the software system meets and conforms to the specified requirements, making certain that all functionalities are tested as intended.

If a defect is considered not genuine or if it's not a real issue, it is typically marked as "Rejected." This status indicates that the defect raised is either not replicable, is intended behavior, or isn't valid in the context it was reported.

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.