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
-
System Testing
-
User Acceptance Testing
-
Operational Testing
-
Readiness Testing
B
Correct answer
Explanation
The standard testing sequence is: Unit Testing → Integration Testing → System Testing → Performance Testing → User Acceptance Testing (UAT). Performance testing validates system responsiveness, load handling, and stability. Once performance is validated, the system moves to UAT where actual users validate business functionality in a production-like environment before go-live.
-
QA Testing
-
Maintenance
-
Implementation
-
User Acceptance Testing
C
Correct answer
Explanation
Post-product validation occurs after the implementation phase but before formal QA testing. It serves as an initial verification that the implemented product meets basic functional requirements before entering more rigorous testing cycles.
-
QA Prime
-
Project Manager
-
Tester
-
All the above
A
Correct answer
Explanation
Execution Set is created by QA Prime in the project workflow. Project Manager and Tester have different roles in project execution and do not create the Execution Set.
-
Specify Requirements-->Specify Release-->Test Execution-->Test Plan-->Manage Defects
-
Specify Release--> Specify Requirements--> Manage defects--> PrepareTest Plan--> Test Execution
-
Specify Release--> Specify Requirements-->Prepare TestPlan-->Test Execution--> Manage Defects
-
Prepare TestPlan--> Specify Requirement--> Manage defects--> Test Execution--> Specify Release
C
Correct answer
Explanation
The correct QC testing process begins with specifying the release (defining scope), then specifying requirements (detailing what to test), preparing the test plan (designing tests), executing tests, and finally managing defects. Options A and B have incorrect ordering.
-
Requirement
-
Release
-
Defect
-
Testcase
A
Correct answer
Explanation
A requirement defines what needs to be tested in an application. Requirements specify the functionality, features, and behaviors that must be verified during testing. They form the basis for creating test cases and determining test scope.
-
Link defect Tab
-
Live anakysis tab
-
Execution flow tab
-
Execution Grid Tab
D
Correct answer
Explanation
The Execution Grid Tab is the standard interface in test management tools for declaring test sets, executing test runs, and reviewing execution results. This tab provides the comprehensive grid view needed for managing test lifecycles. The Link defect Tab is for linking defects, Live analysis is for real-time analytics, and Execution flow is for workflow visualization.
-
New-->Fixed-->Open-->Rejected-->Closed
-
New-->Open-->Fixed-->Rejected-->Closed
-
New-->Reopen-->Closed-->Rejected
-
New-->Fixed-->Open-->Closed
B
Correct answer
Explanation
The standard defect life cycle follows: New→Open→Fixed→Rejected→Closed. A defect starts as New, moves to Open when assigned, to Fixed when resolved, to Rejected if the fix is rejected, and finally to Closed. Option A is incorrect because Fixed comes before Open. Option C is missing the Open state. Option D is missing the Rejected state.
-
Performance
-
Regression
-
Functional
-
Unit
A
Correct answer
Explanation
LoadRunner is primarily a performance testing tool used to simulate user load and measure system behavior under stress. While it can be part of a broader testing strategy, its core purpose is performance and load testing, not functional, regression, or unit testing.
-
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.