Screen "Resolutions" refer to the clarity of the display and how many pixels are contained in it. Ensuring an app is adaptable to various resolutions is crucial to ensure that it looks good and functions properly on diverse devices.

For designing effective test cases, especially for complex systems, a well-documented requirements specification is indispensable. It serves as the foundation, providing clear, unambiguous details about the system's expected behavior. While experienced testers, automation tools, and client feedback are beneficial, the clarity and accuracy of the requirements drive the efficacy of the test cases.

A Test Engineer, sometimes known as a QA Engineer, actively engages in test case execution, identifies software anomalies, and reports defects. While other roles may be involved in the process, the Test Engineer's primary responsibility is to find and report software defects.

Change Control in Configuration Management involves a systematic approach to manage changes by evaluating, approving, or disapproving changes, ensuring that changes are documented, and ensuring that configuration items maintain their integrity throughout the lifecycle.

System testing is conducted on an integrated software to evaluate its complete and end-to-end behavior. It ensures that the entire software functions according to specified requirements. This phase tests the entire software as a single entity.

Although Exploratory Testing can be freestyle, many testers use "Test Charters" to guide their exploration. Test Charters help in providing a clear context, scope, and purpose of the exploration while allowing testers to document and manage their findings efficiently.

The "Exit Criteria" in test planning defines the specific conditions or metrics that need to be achieved before the software can be released. It ensures that the product has reached a certain quality standard before it's deemed fit for production.

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.

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.

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.

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.

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.