Computer Knowledge
Software Testing and Quality Control
2,292 Questions
Software testing and quality control questions cover testing methodologies, unit testing, and defect management. These concepts are crucial for the computer knowledge sections of competitive exams. Practice these questions to understand verification and validation processes thoroughly.
Quality control typesUnit testing purposeSoftware vulnerability testingTest planning tasksLoop testing criteriaTest harness functions
Software Testing and Quality Control Questions
-
Compatability testing
-
Compliance testing
-
Interoperability testing
-
Performance testing
B
Correct answer
Explanation
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'.
-
Soak testing
-
Scalability tetsing
-
Usability testing
-
Acceptance testing
C
Correct answer
Explanation
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
-
Reliability testing
-
Performance testing
-
Load testing
A
Correct answer
Explanation
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.
-
Load testing
-
Stress testing
-
Performance testing
-
Recovery testing
B
Correct answer
Explanation
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
-
Stress testing
-
Performance testing
-
Reliability testing
A
Correct answer
Explanation
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'.
-
User friendliness
-
whether important information is presented in a comprehensible way
-
Only A
-
A and B
D
Correct answer
Explanation
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.
-
volume testing
-
Stress testing
-
Load testing
-
Performance testing
C
Correct answer
Explanation
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.
-
Stress testing
-
Load testing
-
Volume testing
-
Performance testing
D
Correct answer
Explanation
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.
-
Recovery testing
-
Load testing
-
Reliability testing
-
Stress testing
D
Correct answer
Explanation
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.
-
Compatability testing
-
Compliance testing
-
Reliability testing
-
Performance testing
B
Correct answer
Explanation
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.
-
Soak testing
-
Scalability tetsing
-
Usability testing
-
Acceptance testing
C
Correct answer
Explanation
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
-
Reliability testing
-
Performance testing
-
Load testing
A
Correct answer
Explanation
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.
-
Load testing
-
Stress testing
-
Performance testing
-
Recovery testing
B
Correct answer
Explanation
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.
-
volume testing
-
Stress testing
-
Load testing
-
Performance testing
C
Correct answer
Explanation
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.
-
stress testing
-
Load testing
-
volume testing
-
performance testing
D
Correct answer
Explanation
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.