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
-
Breadth Test and Depth Test
-
Retesting
-
Confirmation Testing
-
Sanity Testing
A
Correct answer
Explanation
Maintenance testing uses breadth testing for comprehensive coverage across the system and depth testing for thorough examination of affected areas. Retesting and confirmation testing are similar techniques but not the primary methodologies, while sanity testing is a different category altogether.
-
Structural Testing
-
Design Based Testing
-
Error Guessing Technique
-
Experience Based Technique
A
Correct answer
Explanation
White box testing examines the internal code structure and implementation details of software, which is why it's alternatively called structural testing. Design-based testing, error guessing, and experience-based techniques are distinct testing approaches.
-
A set of test cases for testing classes of objects
-
An input or output range of values such that only one value in the range becomes a test case
-
An input or output range of values such that each value in the range becomes a test case
-
An input or output range of values such that every tenth value in the range becomes a test case.
B
Correct answer
Explanation
An equivalence partition groups input values that are expected to produce similar results, so testing one value from the group is sufficient to represent the entire partition. This is the core principle of equivalence partitioning - one value represents the whole range.
-
Are most useful in uncovering defects in the process flows during real world use of the system
-
Are most useful in uncovering defects in the process flows during the testing use of the system
-
Are most useful in covering the defects in the process flows during real world use of the system
-
Are most useful in covering the defects at the Integration Level
A
Correct answer
Explanation
Use case test cases are most valuable for uncovering defects in process flows during real-world system usage because they simulate actual user scenarios. The key distinction in the options is between 'real world use' and 'testing use' - real-world usage is where use cases shine.
-
Creating test suites from the test cases
-
Executing test cases either manually or by using test execution tools
-
Comparing actual results
-
Designing the Tests
D
Correct answer
Explanation
Test implementation and execution involves creating test suites from test cases, executing them manually or with tools, and comparing actual results with expected results. Designing tests is part of the earlier test design phase, not implementation and execution.
-
ii is True; i, iii, iv & v are False
-
i,ii,iii are true and iv is false
-
ii & iii are True; i, iv are False
-
ii, iii & iv are True; i is false
B
Correct answer
Explanation
A risk-based approach uses identified risks to determine the test techniques, the depth of testing required, and to prioritize tests to find critical bugs early. Project cost estimation is a project management activity, not a function of testing risks, making statements i, ii, and iii true and iv false.
-
i, ii, iii is true and iv is false
-
ii,iii,iv is true and i is false
-
i is true and ii,iii,iv are false
-
iii and iv is correct and i and ii are incorrect
B
Correct answer
Explanation
According to standard ISTQB testing guidelines, designing test specifications, preparing test data, and executing/logging tests are core tasks of a tester. Interacting with tool vendors to leverage tools on the project is typically a test manager's responsibility, making statement i false and statements ii, iii, and iv true.
-
Checking for existence of latest architecture overview document.
-
Checking the performance of the oracle service from connected entities.
-
Checking for creation of log files.
-
None of the above
B
Correct answer
Explanation
OAT (Oracle Application Testing) focuses on validating documentation existence and log file creation, but does not include performance testing of the Oracle service from connected entities. This specific performance check falls outside the standard OAT testing scope and requires separate testing tools or methodologies.
-
Test Plan
-
Tracebility Matrices
-
Test Completion report
-
All
D
Correct answer
Explanation
System testing produces multiple key documents throughout its lifecycle: a Test Plan outlines the approach, Traceability Matrices map requirements to test cases, and a Test Completion Report summarizes results. All three are standard deliverables from a system testing phase.
-
DTP(Detail Test Plan)
-
MTP(Master Test Plan)
-
STP(System Test Plan)
-
Tracebility Matrices
C
Correct answer
Explanation
At the start of System Testing, the System Test Plan (STP) is prepared. This document defines the scope, approach, resources, and schedule for system-level testing. DTP (Detail Test Plan) comes later for specific test cases, MTP (Master Test Plan) is for overall test strategy across all test levels, and Traceability Matrices are prepared during test planning.
-
Test tab
-
Test Plan
-
Defects tab
-
All
B
Correct answer
Explanation
Test Plans are the designated tab or section in test management tools where test scripts and test cases are uploaded, organized, and executed. Test tabs typically show test execution status, while Defects tabs track bugs.
-
QC Install Checker
-
Quality Center Checker
-
QC Install Inspector
-
QC Install Check
B
Correct answer
Explanation
Quality Center Checker is the official tool used to verify that HP Quality Center (formerly TestDirector/QuickTest Professional QC) has been installed properly. It checks all components, database connectivity, permissions, and configuration settings. The other options (QC Install Checker, QC Install Inspector, QC Install Check) are not the correct names of the official verification tool for Quality Center installations.
-
Test
-
Test Run
-
Test Step
-
Test Set
C
Correct answer
Explanation
When a defect is raised during a manual test run in Quality Center, it is directly linked to the specific Test Step that failed. This provides traceability from the defect to the exact step in the test case where the issue was detected. The defect is not directly linked to the Test (test case), Test Run (the execution instance), or Test Set (the collection of tests). The Test Step linkage allows precise identification of where in the test flow the defect occurred.
-
Test
-
Test Run
-
Test Step
-
Test Set
C
Correct answer
Explanation
When a defect is raised during a manual test run in Quality Center, it is directly linked to the specific Test Step that failed. This provides traceability from the defect to the exact step in the test case where the issue was detected. The defect is not directly linked to the Test (test case), Test Run (the execution instance), or Test Set (the collection of tests). The Test Step linkage allows precise identification of where in the test flow the defect occurred.
-
QC Install Checker
-
Quality Center Checker
-
QC Install Inspector
-
QC Install Check
B
Correct answer
Explanation
Quality Center Checker is the official tool used to verify that HP Quality Center (formerly TestDirector/QuickTest Professional QC) has been installed properly. It checks all components, database connectivity, permissions, and configuration settings. The other options (QC Install Checker, QC Install Inspector, QC Install Check) are not the correct names of the official verification tool for Quality Center installations.