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
-
i, iii. and iv. are more for developers.
-
ii. and iv. are more for developers.
-
ii, iii. and iv. are more for developers.
-
ii. and iii. are more for developers.
B
Correct answer
Explanation
Coverage measurement tools help developers identify which code paths haven't been executed. Dynamic analysis tools detect runtime issues like memory leaks. Performance testing typically requires QA specialists, test comparators serve testers, and incident management is used across the team.
-
Unreachable code.
-
Unreachable Variables
-
Faults in the requirements
-
Too few comments
C
Correct answer
Explanation
Static code analysis examines source code structure to identify issues like unreachable code, unused variables, and insufficient comments. It cannot detect faults in requirements because requirements are not code - they are separate documents that static analysis tools don't process.
-
Boundary Testing
-
Ad Hoc Testing
-
Functional Testing
-
Mutation Testing
B
Correct answer
Explanation
Ad Hoc testing is unstructured, exploratory testing where testers randomly try various functionality to find unexpected defects. Boundary testing checks edge values, Functional testing validates requirements, and Mutation testing modifies code to verify test suite quality. 'Breaking the system randomly' is the hallmark of Ad Hoc.
-
Ad Hoc Testing
-
Compatibility Testing
-
Endurance Testing
-
Functional Testing
C
Correct answer
Explanation
Endurance testing (also called soak testing) evaluates system stability over prolonged periods to detect issues like memory leaks, resource exhaustion, or slow degradation that only appear after extended runtime. Ad Hoc is random exploration, Compatibility checks cross-platform behavior, and Functional testing validates features.
-
Component Testing
-
Scalability Testing
-
Ad Hoc Testing
-
Agile Testing
D
Correct answer
Explanation
Agile Testing is a practice in agile development where testing is integrated throughout the development lifecycle, with development treating testing as its customer and emphasizing test-first design through techniques like TDD. It promotes continuous testing alongside development rather than as a separate phase.
-
Agile Testing
-
Functional Testing
-
Acceptance Testing
-
Smoke Testing
C
Correct answer
Explanation
Acceptance testing is performed by customers or users to verify if the software meets business requirements and is ready for deployment. Agile testing is a development methodology, functional testing focuses on feature correctness, and smoke testing verifies basic build stability rather than final acceptance.
-
Component Testing
-
Exhaustive Testing
-
End-to-End Testing
-
Functional Testing
B
Correct answer
Explanation
Exhaustive Testing aims to test every possible combination of inputs and preconditions. While theoretically complete, it's usually impractical for real-world systems due to the exponential growth of test cases with each input variable.
-
Component Testing
-
Functional Testing
-
Regression Testing
-
Smoke Testing
D
Correct answer
Explanation
Smoke testing is a preliminary testing cycle designed to ensure that the basic and most critical capabilities of a software application function correctly before proceeding to deeper test suites. Distractors like regression, functional, or component testing refer to more structured, targeted, or comprehensive testing methods.
-
Soak testing
-
Smoke testing
-
Agile Testing
-
Functional Testing
A
Correct answer
Explanation
Soak testing involves running a system under high load for an extended period to identify issues like memory leaks, performance degradation, or resource exhaustion that only appear over time. It helps ensure system stability during prolonged operation.
-
Component Testing
-
Stress Testing
-
Dynamic Testing
-
Recovery Testing
B
Correct answer
Explanation
Stress Testing pushes a system beyond its specified limits to determine breaking points and observe failure modes. It helps identify the maximum load capacity and how the system degrades or fails under extreme conditions, unlike normal load testing which stays within specifications.
-
Black Box Testing
-
Acceptance Testing
-
User Acceptance testing
-
Boundary Testing
C
Correct answer
Explanation
User Acceptance Testing (UAT) is the final testing phase where actual users validate the software against real-world requirements before purchase or deployment. While Acceptance Testing is a broader category that may include internal QA, UAT specifically involves end users performing formal evaluation as a condition of purchase.
-
Scalability Testing
-
Benchmark Testing
-
Mutation Testing
-
Black Box Testing
B
Correct answer
Explanation
Benchmark testing uses standardized, representative workloads to measure and compare system performance across different hardware or software configurations. It establishes baseline performance metrics by running typical programs and data sets through the system being evaluated.
-
Mutation Testing
-
Component Testing
-
Agile Testing
-
Ad Hoc Testing
A
Correct answer
Explanation
Mutation testing intentionally injects small code changes (mutations) to create faulty versions of the application, then runs existing tests against them. If tests fail to catch the injected bugs, it indicates the test suite needs improvement. Mutation testing evaluates test suite quality rather than application correctness.
-
Boundary Testing
-
Smoke Testing
-
Scalability Testing
-
Functional Testing
C
Correct answer
Explanation
Scalability testing measures system performance under increasing workload to determine when or if the system degrades. Unlike basic performance testing, scalability testing specifically focuses on graceful handling of growth and helps identify capacity limits before production failure.
-
test items
-
test deliverables
-
test tasks
-
test environment
-
test specification
E
Correct answer
Explanation
IEEE 829 standard for software test documentation includes sections for test items, test deliverables, test tasks, and test environment. Test specification is not one of the standard document names - the actual documents are Test Design Specification, Test Case Specification, and Test Procedure Specification as separate entities.