Computer Knowledge
Software Testing and Quality Control
2,598 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
-
Black box testing
-
Regression Testing
-
Integration testing
-
Performance Testing
B
Correct answer
Explanation
Regression testing specifically checks that recent code or configuration changes haven't adversely affected existing features. When any module is modified, regression testing validates that the entire application still functions correctly, catching unintended side effects.
-
Usability Testing
-
User Acceptance Testing
-
Performance Testing
-
Compatability Testing
A
Correct answer
Explanation
Usability testing directly measures how easily users can interact with a system - evaluating user-friendliness through factors like learnability, efficiency, memorability, error prevention, and user satisfaction. User Acceptance Testing (UAT) is different - it validates business requirements before deployment.
-
System Testing
-
Black box testing
-
Unit testing
-
White box testing
B
Correct answer
Explanation
Black box testing validates functionality based on requirements without examining internal code structure. Testers focus on inputs and outputs against functional specifications, making it ideal for testing based on functional requirements. System testing is broader (entire system), while unit testing is narrower (individual components).
-
Unit testing
-
Glass box testing
-
Black box testing
-
Functional Testing
B
Correct answer
Explanation
Glass box testing (also called white box or clear box testing) examines internal code structure, logic flow, algorithms, and implementation details. Testers need knowledge of the code's internal workings to design tests. This directly matches 'testing based on internal logic'.
-
Incremental Integration testing
-
System Testing
-
Integration testing
-
Unit testing
A
Correct answer
Explanation
Incremental integration testing continuously validates integrated modules as new functionality is added. Each increment is tested immediately upon integration, ensuring smooth ongoing integration rather than waiting until all features are complete.
-
Testing a software by compiling and running it
-
Model-based testing methodology for the reactive test of dynamical or control systems
-
Form of software testing where the software isn't actually used
-
None of the above
C
Correct answer
Explanation
Static testing examines software artifacts (requirements, design documents, code) without executing the program. It includes reviews, walkthroughs, and inspections. Options A and C both describe aspects of testing, but C is more precise for static testing. Option B describes model-based testing, which is dynamic.
-
System Testing
-
Acceptance Testing
-
System Integration Testing
-
Data Migration Testing
B
Correct answer
Explanation
Acceptance testing is primarily designed to establish confidence in the system and demonstrate that it meets user needs and business requirements, rather than finding defects. Conversely, system, integration, and migration testing are focused directly on identifying and fixing defects.
-
System testing
-
Usability testing
-
Performance testing
-
Both b and c
D
Correct answer
Explanation
Non-functional testing evaluates system characteristics rather than specific behaviors. Performance testing measures speed, scalability, and stability. Usability testing assesses user experience. Both are non-functional. System testing is functional (validates features work correctly).
-
Performance testing, load testing, stress testing are part of functionality
-
Tests are based on functions and features and their interoperability with specific systems
-
Includes the tests required to measure characteristics of systems
-
It is the testing of “how” the system works
B
Correct answer
Explanation
Functional testing validates what the system does - its features, functions, and interoperability. Option B correctly describes this. Option A lists non-functional tests (performance, load, stress). Option C describes non-functional characteristics. Option D is incorrect - functional testing tests 'what' the system does, not 'how' it works internally.
-
Quick Test Professional
-
Load Runner
-
Quality Center
-
Jmeter
C
Correct answer
Explanation
Test management tools organize test cases, execution, and reporting. Quality Center (now HP ALM) is a comprehensive test management tool. Quick Test Professional is automated functional testing. Load Runner is performance testing. JMeter is load/performance testing. Only Quality Center manages the entire testing process.
-
Checking whether the software is built right
-
Matching the software developed, with the specifications
-
Checking whether the right software is built
-
Matching the software developed, with only requirements
C
Correct answer
Explanation
Validation determines whether the software meets the user's actual needs, which is commonly summarized as building the right software. Verification, by contrast, is checking if the software was built right according to the specifications, which makes the other options incorrect.
-
Test management tool
-
Capture/Playback
-
Boundary Tester
-
Data Comparator
B
Correct answer
Explanation
Regression testing verifies that existing functionality still works after changes. Capture/Playback tools record test actions and replay them automatically, making them ideal for repeated regression tests. Test management tools organize tests but don't execute them. Boundary testers focus on edge cases, not regression. Data comparators validate data integrity.
-
Mutation Testing
-
Specification-based testing
-
Fault Injection
-
Code coverage
B
Correct answer
Explanation
White-box testing examines internal code structure. Mutation Testing alters code to verify tests catch changes. Fault Injection introduces errors to test system response. Code coverage measures how much code is executed. Specification-based testing uses requirements without code knowledge - it's black-box, not white-box.
-
Destructive testing
-
Usability testing
-
Stability testing
-
Security testing
D
Correct answer
Explanation
Security testing is essential for software handling confidential data as it identifies vulnerabilities that hackers could exploit to intrude into the system. Destructive testing tests system stability under stress, usability testing evaluates user experience, and stability testing checks system reliability under load - none specifically address hacker intrusion prevention.
-
A collection of tests that are performed to decide whether it is possible to proceed with further testing.
-
A collection of tests that are performed to decide whether it is reasonable to proceed with further testing.
-
Build Validation test
-
Testing done by end users
A
Correct answer
Explanation
Smoke testing is a quick, initial suite of tests run on a new build to determine if the software is stable enough to proceed with further, more detailed testing. Distractors like end-user testing refer to acceptance testing, while the distinction between possible and reasonable is minor.