Stability: Stress testing aims to determine a system's robustness by pushing it beyond its limits. When the system fails, it's crucial to assess its stability in terms of recovery and ensure that it doesn't compromise the data integrity and returns to its stable state.

For mobile apps, it's imperative to test both Landscape and Portrait modes when conducting functional testing. This ensures that the application's functionality remains consistent and error-free regardless of the orientation. Given that users might switch between modes frequently, it's crucial to verify the app's behavior in both scenarios.

Data-driven scripting allows the separation of test scripts from the test data. This means one script can be executed with multiple sets of test data. As a result, the number of scripts needed is reduced, making test automation more efficient and manageable. You can test various scenarios using the same script by merely changing the input data.

Stress testing involves deliberately overloading the system beyond its specified limits. The objective is to identify system weak points, ensure it fails gracefully, and understand how it behaves under extreme conditions.

Version Control systems allow multiple developers to work on the same project concurrently. When two developers make changes to the same piece of code, the version control system flags it as a merge conflict. The developers, possibly with the help of a lead or reviewer, will then resolve the conflict, ensuring that the final merged code retains the intended functionality from both changes.

The Test Lead is usually responsible for managing and leading the test team, which includes making key decisions related to test issues. While a Test Manager might have overarching responsibility and a Business Analyst might provide business perspective, it is the Test Lead who usually determines the severity and priority of a bug.

Automated testing is particularly suitable for regression tests, which need to be executed frequently to ensure that previously working functionality remains intact after any code changes or updates.

A "Scenario" in usability testing refers to a specific set of tasks that participants are asked to perform. It's a narrative that describes the user's actions and intentions without suggesting how they might be accomplished. This helps to evaluate the product's ease of use and intuitiveness in a real-world context.

Configuration Auditing and Configuration Control are both crucial aspects of Configuration Management. Configuration Auditing ensures that the current configuration of an item matches the specified requirements and checks for consistency and completeness, ensuring no unauthorized changes have occurred. On the other hand, Configuration Control involves evaluating, coordinating, approving or disapproving, and implementing changes to configured items.

Linting is a process that involves the use of tools (often termed as "linters") to automatically scan source code for potential issues. These tools typically focus on ensuring that coding standards, conventions, and best practices are adhered to, without executing the program or script.