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
-
will help ensue unchanged areas of the software have not been affected
-
can only be run during user acceptance testing
-
will help ensure changed areas of the software have not been affected
-
will always be automed
A
Correct answer
Explanation
Regression testing verifies that recent code changes haven't adversely affected existing features - it specifically checks unchanged areas of the software to ensure they still work. Option C is incorrect because regression testing focuses on unchanged areas, not changed ones. Option B is wrong because regression testing runs at all levels, not just UAT. Option D is incorrect because regression tests can be manual.
-
Does not meet people needs
-
Loss of control over reallocation of resources
-
Cultural difference
-
Relinquishments of control
C
Correct answer
Explanation
Testing offshore software (outside your country) primarily introduces cultural differences in communication, work practices, language interpretation, and business context understanding. Options A (people needs) and D (relinquishing control) are vague concerns, not specific differences. Option B (resource reallocation) is an operational issue, not a unique offshore challenge. Cultural differences are the most distinct factor.
-
2 is a valid reason; 1,3,4&5 are not
-
1,2,3,4 are valid reasons; 5 is not
-
1,2,3 are valid reasons; 4&5 are not
-
All of them are valid
D
Correct answer
Explanation
Software failures can stem from multiple sources: testing faults (errors in test design/execution), software faults (bugs in code), design faults (flaws in architecture/design), environment faults (infrastructure/dependency issues), and documentation faults (incorrect specs). All five are valid root causes of test failures. Option D correctly recognizes that all are legitimate reasons.
-
After Coding
-
After external design
-
After internal design
-
After freezing the requirements
D
Correct answer
Explanation
Testing should begin as early as possible in the lifecycle - after requirements are frozen (Option D) because this is when test planning and design can start with stable, clear specifications. Waiting until after coding (A), external design (B), or internal design (C) delays test preparation and increases the risk of requirement misunderstandings. Early testing saves cost and catches defects sooner.
-
it may be difficult to repeat the test
-
It will be difficult to decide if the test has passed or failed
-
We cannot run the test
-
We cannot automate the user inputs
B
Correct answer
Explanation
Without a specified acceptance criterion or expected result, you cannot determine whether a test passed or failed - this is the fundamental pass/fail decision point. Option A (repeatability) and C (execution) are still possible without criteria. Option D (automation) is also possible - you can automate inputs even if pass/fail is unclear. The core issue is the inability to judge results.
-
Simple Loops
-
Nested Loops
-
Concatenated Loops
-
All of the above
D
Correct answer
Explanation
Loop testing methodology applies to all loop structures: simple loops (single iterations), nested loops (loops within loops), and concatenated loops (loops in sequence). The technique tests boundary conditions, typical cases, and stress scenarios for each structure type. Option D correctly includes all categories. Options A-C are each incomplete subsets.
-
Shorten the time required for testing
-
Find more faults
-
Do more effective testing
-
Do the best testing in the time available
D
Correct answer
Explanation
Test prioritization's core purpose is optimizing the use of limited testing time - it ensures that the most important tests (highest risk/business value) are executed first within time constraints. Option D captures this - doing the BEST testing in available time. Options A (shorten time), B (find more faults), and C (effective testing) are desirable outcomes but not the primary reason for prioritization itself.
-
Having good attention to detail
-
Being diplomatic
-
Able to be relied on
-
Able to write software
-
Test Factors
-
Functions/subroutines
-
All of the above
-
None of the above
C
Correct answer
Explanation
Comprehensive test data collection should include both qualitative and quantitative metrics, such as test factors, functions/subroutines executed, code coverage, and defect counts. Thus, 'All of the above' is correct.
-
Checking that we are building the right system
-
Checking that we are building the system right
-
Performed by an independent test team
-
Making sure that it is what the user really wants
B
Correct answer
Explanation
Verification ensures that the software conforms to its specified requirements ('building the system right'). Validation, on the other hand, ensures that the software meets the user's actual needs ('building the right system').
-
use test appropriate metrics
-
declare that it is over when budget is consumed
-
let the management decide that
-
declare that it is ove when time is out
A
Correct answer
Explanation
To determine when testing is complete with confidence, teams should use objective, predefined test metrics (such as code coverage or defect density) rather than arbitrary constraints like running out of time or budget.
-
Compliance Testing - Business rules
-
Black Box Testing - Path Coverage
-
Regression Testing - End users
-
File Integrity - Control Totals
D
Correct answer
Explanation
File verification using Control Totals (summing numeric fields) validates data integrity by comparing calculated totals against expected values. The other pairings are incorrect: Compliance testing uses compliance checklists not business rules; Black box tests functionality not internal paths; Regression testing is done by testers, not end users.
-
Green box
-
Black box
-
Yellow box
-
White box
D
Correct answer
Explanation
Cyclomatic Complexity measures code's decision-based complexity by counting independent paths through control flow (V(G) = E - N + 2P). This requires analyzing source code structure - a white box testing method. Black box testing examines external behavior without seeing code.
-
Set up Test environment, Identify test cases and test cycles, Review test results, Assign test scripts
-
Identify test cases and test cycles, Assign test scripts, set up test environment, review test results
-
Set up test environment, identify test cases and test cycles, assign test scripts, review test results
-
All of the above
C
Correct answer
Explanation
Test execution follows a logical sequence: first set up the environment (infrastructure, test data), then identify which test cases to run, assign scripts to testers, execute them, and finally review results. Option C matches this workflow. Options A and B have ordering errors.
-
A small team to establish the best way to use the tool
-
The vendor contractor to write the initial scripts
-
Everyone who may eventually have some use for the tool
-
The independent testin team
A
Correct answer
Explanation
New testing tools should be piloted by a small team first to establish best practices, identify pitfalls, and create usage guidelines before organization-wide rollout. This prevents widespread misuse, inefficiency, and tool abandonment. Vendors shouldn't write initial scripts - internal testers must understand the tool themselves.