Software Testing Types and Methodologies

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.

Recovery testing verifies that a system can recover from failures and maintain data integrity after unexpected events like system restarts. Reliability testing focuses on consistent performance, performance testing measures speed, and load testing applies expected demand.

Stress testing evaluates system behavior under extreme conditions like DoS attacks or sudden massive traffic spikes. Load testing uses expected demand, performance testing measures speed, and recovery testing checks recovery after failures.

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.

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, interoperability testing ensures data exchange, 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.

Recovery testing verifies a system's ability to recover from crashes, hardware failures, or other catastrophes. Restarting the computer while an application runs and then checking data integrity is a classic recovery test scenario. Load testing measures performance under expected load, not recovery. Performance testing is a broader category that includes load testing. Reliability testing focuses on consistent behavior over time, not recovery from failures.

Stress testing evaluates system stability under extreme, spike, or beyond-limit conditions such as a DoS attack or sudden user spikes. Load testing determines behavior under expected peak loads, while recovery testing measures recovery speed.

Load testing measures system performance under expected user loads. Testing response times at 500, 750, and 1000 users is classic load testing - checking how the system performs at various load levels within expected capacity. Stress testing goes beyond expected load to find breaking points. Performance testing is the broader umbrella category that includes both load and stress testing.

Ergonomics testing (or usability testing) focuses on how well the UI presents information and how easy it is for users to understand and interact with the system. Option B directly addresses whether information is comprehensibly presented, which is core to ergonomics. Option A mentions 'without prototype' which doesn't define what ergonomics tests - it's not about whether a prototype exists, but about the comprehensibility of the interface itself.

The Watch tab in the Debug Viewer allows you to monitor the current value of any variable or VBScript expression during test execution. You can add specific variables or expressions to watch and see their values update in real-time as the test progresses.

The Variables tab in the Debug Viewer displays all variables that have been declared or used up to the current point in the test execution. It shows the current value of each variable, providing a comprehensive view of the test's variable state at any breakpoint.

The Command tab in the Debug Viewer allows you to execute VBScript statements during a debugging session. You can use it to set or modify variable values, test expressions, or execute any VBScript command to understand or manipulate the test state at runtime.