Software Testing and Quality Control

Static testing evaluates software artifacts without executing the code. Code inspection is a manual review process where developers examine code for defects without running it - this is static testing. Coverage analysis and installation testing require code execution.

Load testing is specifically defined as the process of putting demand on a system and measuring its response. It involves testing the system under a specific expected load to determine behavior. Stress testing tests beyond normal load (often to breaking point), volume testing focuses on data volume, and performance testing is a broader category measuring speed, responsiveness, and stability under various conditions. Load testing is the most precise match to 'putting demand and measuring response'.

Performance testing is the broad category that specifically measures how fast aspects of a system perform under a particular workload. It focuses on response times, throughput, and latency metrics. Load testing is a subset of performance testing that tests under specific loads. Stress testing tests beyond normal capacity. The misspelling 'Volume esting' is likely a typo for Volume Testing. Performance testing best matches the definition of testing speed under workload.

Stress testing is specifically used to determine the stability of a system by testing it beyond normal operating conditions, often pushing it to breaking point. It evaluates system stability and robustness under extreme conditions. Recovery testing focuses on recovery from failures, reliability testing measures consistency over time, and load testing tests under expected loads. Stress testing's primary goal is assessing stability under adverse conditions.

Compliance testing (also called conformance testing) specifically determines whether a product meets specified standards for efficiency, interoperability, or other defined criteria. Compatibility testing checks if the system works with different platforms/environments, interoperability testing tests interaction between systems, and performance testing measures speed. Compliance testing is the correct match for 'meeting specified standards'.

Usability testing specifically involves observing real users using the product to discover errors and areas for improvement. It focuses on the user experience, ease of use, and user satisfaction. Soak testing tests longevity, scalability testing tests ability to scale up, and acceptance testing determines if requirements are met. Usability testing directly matches 'observing people using the product to discover errors and improvements'. Option B also has a typo 'tetsing' instead of 'testing'.

Recovery testing specifically tests how well a system recovers from crashes, failures, or unexpected conditions like sudden restarts. It verifies that data integrity is maintained and the system can properly restore itself after crashes. The scenario describes exactly what recovery testing is - restart the computer while application is running, then check data integrity. Reliability, performance, and load testing don't focus on crash recovery scenarios.

Stress testing tests systems under extreme or excessive loads beyond normal operating conditions. The scenario describes excessive volume - either DoS attacks or sudden massive traffic surges (widely viewed news item causing traffic spikes). These are extreme conditions beyond normal expected load. Load testing tests under expected loads, performance testing measures speed, and recovery testing tests crash recovery. Stress testing is specifically designed for these excessive overload scenarios.

Load testing specifically tests system behavior under expected user loads by measuring response times at various load levels (500, 750, 1000 users as mentioned). The key characteristic is testing at SPECIFIC increasing load levels and measuring response. Stress testing tests beyond normal load, performance testing is broader, and reliability testing focuses on consistency. Load testing with its graduated load measurement perfectly matches 'testing response time at various levels of load'.

Ergonomics testing (or HCI testing) encompasses both user friendliness (ease of use, intuitiveness) AND whether important information is presented comprehensibly. Option A covers user friendliness, Option B covers information comprehensibility. Since ergonomics testing includes BOTH aspects, 'A and B' is the correct answer. Only A (Option C) is incomplete, and individual options A or B capture only half of what ergonomics testing evaluates.

Load testing is the process of applying demand to a system and measuring its response under expected or normal conditions. Volume testing focuses on data volume, stress testing pushes beyond capacity, and performance testing is the broader category that includes load testing.

Performance testing specifically measures how fast system aspects perform under particular workloads. While load testing applies demand, performance testing focuses on measuring speed and responsiveness metrics.

Stress testing determines system stability by pushing it beyond normal operating conditions to identify breaking points. Recovery testing checks recovery after failures, load testing measures response under expected demand, and reliability testing focuses on consistent performance over time.

Compliance testing verifies that a product meets specified standards for efficiency, interoperability, or other defined criteria. Compatibility testing checks if systems work together, reliability testing measures consistent performance, and performance testing measures speed.

Usability testing involves observing real users interacting with a product to identify errors, usability issues, and improvement opportunities. Soak testing tests for memory leaks over time, scalability testing handles growth, and acceptance testing validates requirements.