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
-
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.
-
A black box testing technique than can only be used during system testing
-
A white box testing technique appropriate for component testing
-
A black box testing technique used only by developers
-
A black box testing technique appropriate to all levels of testing
D
Correct answer
Explanation
Equivalence partitioning is a black-box testing technique that divides input data into partitions of equivalent data. It is highly versatile and can be applied at all levels of testing, from unit testing to system testing.
-
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 functionality. It targets unchanged areas to ensure no unintended side effects occurred. It's not limited to UAT (runs throughout testing), doesn't validate changed areas (that's unit/system testing), and isn't always automated (often manual). Note: 'automed' appears to be a typo for 'automated'.
-
Does not meet people needs
-
Loss of control over reallocation of resources
-
Cultural difference
-
Relinquishments of control
C
Correct answer
Explanation
When testing software developed by contractors in different countries, cultural differences significantly impact communication, work practices, requirements interpretation, and testing approaches. These differences can lead to misunderstandings about specifications, testing standards, and defect reporting. Options A and D are not inherent differences of international contracting, while resource reallocation (B) is a general management concern, not specific to international vs domestic.
-
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
A system failure can be caused by various issues, including testing faults, software bugs, design flaws, environment configuration issues, or incorrect documentation. Therefore, all of these are valid reasons for a failure.
-
After Coding
-
After external design
-
After internal design
-
After freezing the requirements
D
Correct answer
Explanation
Starting testing after requirements are frozen allows test planning and design to align with stable specifications, enabling early identification of issues and more comprehensive test coverage. Testing should begin as early as possible in the lifecycle - waiting until after coding (A), internal design (C), or external design (B) is complete delays defect detection and increases cost. Requirements freezing marks when specs are stable enough to begin detailed test preparation.
-
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, a tester cannot objectively compare the actual outcome of a test against a standard, making it difficult to determine whether the test passed or failed.
-
Simple Loops
-
Nested Loops
-
Concatenated Loops
-
All of the above
D
Correct answer
Explanation
Loop testing is a white-box testing technique that focuses on the validity of loop constructs. It can be applied to all types of loops, including simple loops, nested loops, and concatenated loops.
-
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 ensures the most critical and high-risk tests are executed when time is limited, maximizing the value of testing within constraints. Shortening time (A) is about efficiency, not prioritization. Finding more faults (B) depends on test quality, not order. Being more effective (C) is vague - the key is doing the best possible testing given available time (D). Prioritization accepts that not everything can be tested.