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
-
re-testing looks for unexpected side-effects; regression testing ensures the original fault has been removed
-
re-testing is done after faults are fixed; regression testing is done earlier
-
re-testing is done by developers; regression testing is done by independent testers
-
re-testing ensures the original fault has been removed; regression testing looks for unexpected side-effects
D
Correct answer
Explanation
Re-testing (or confirmation testing) runs the same test cases to confirm a specific defect is fixed. Regression testing runs tests on unchanged parts of the system to ensure no new defects or side-effects were introduced by changes.
-
yes, because testing includes all non-constructive activities
-
no, because they apply to development documentation
-
yes, because both help detect faults and improve quality
-
no, because they are normally applied before testing
C
Correct answer
Explanation
Reviews and inspections are static testing techniques that examine documentation or code without execution. Like dynamic testing, their purpose is detecting defects and improving quality, making them part of the broader testing discipline. Static testing finds faults earlier and cheaper than dynamic testing, complementing test execution. The testing lifecycle includes both static and dynamic techniques.
-
as the first approach to deriving test cases
-
by inexperienced testers
-
after more formal techniques have been applied
-
after the system has gone live
C
Correct answer
Explanation
Error guessing is an experience-based, informal technique. It is most effective as a complement after formal, systematic techniques (like boundary value analysis) have been applied to ensure no obvious gaps remain uncovered.
-
when the test completion criteria have been met
-
when all planned tests have been run
-
when no faults have been found by the tests run
-
when time for testing has run out
A
Correct answer
Explanation
Testing should stop when defined exit criteria (completion criteria) are met, ensuring objective quality goals are satisfied. Running out of time or tests is resource-based, not quality-based, and finding no faults may just mean tests are ineffective.
-
Yes,the test can be recovered from the Unattached folder
-
No, once a test is deleted .it is gone
-
Yes,the tests can be recovered from the Subject folder
-
No,only Project Manager have permission to recover deleted tests
A
Correct answer
Explanation
In HP Quality Center's Test Plan module, deleting a folder does not permanently delete the tests immediately; instead, the tests are moved to the system-created 'Unattached' folder, allowing recovery. They do not go to the Subject folder, and they are not permanently deleted right away.
-
From the Requiremnts module
-
On the test details page (Test Plan)
-
On the attachments page(TestPlan)
-
From The Test Lab module
A
Correct answer
Explanation
In the Requirements module, you select requirements and use the 'Cover' or 'Add Test' buttons to link tests to requirements. While you can see requirements on test details, the actual linking happens from Requirements module. Test Lab is for execution, not linking.
-
Testcases
-
Repository
-
Load test
-
Defects
B
Correct answer
Explanation
Quality Center is fundamentally a repository - it stores and manages test assets (requirements, tests, defects, cycles). 'Testcases' and 'Defects' are items within the repository, not its main function. Load testing is separate functionality.
-
Requirement and Defect
-
Requirement,Test Plan,Test Lab and Defect
-
Requirement,Test Plan and Defect
-
Defect
B
Correct answer
Explanation
In Quality Center/ALM, defects can be logged from multiple modules to provide flexibility throughout the testing lifecycle. The Defect module itself is the primary location, but you can also log defects directly from the Requirements module (when reviewing requirements), Test Plan module (during test design/execution), and Test Lab module (while running tests). This integrated workflow allows testers to capture issues immediately upon discovery, regardless of which module they are working in.
-
Details
-
Design Steps
-
Test Script
-
Req Coverage
B
Correct answer
Explanation
In the Test Plan module of Quality Center/ALM, the Design Steps tab contains the detailed test steps where you can specify manual or automated execution. This tab provides the option to convert a manual test (with defined steps) into an automated test by associating it with an automated test script or tool. The Details tab contains general test metadata, Test Script is for actual automation code, and Req Coverage shows requirement mappings.
-
Non-functional(Excluding Performance Testing)
-
Non Functional(Including Performance Testing)
-
Functional
-
All of the above
-
None of the above
A
Correct answer
Explanation
OAT (Operational Acceptance Testing) performs non-functional testing such as security, usability, reliability, and compatibility testing, but excludes performance testing. Option A correctly describes this scope. Options B incorrectly includes performance testing, while C incorrectly suggests functional testing which is done in other phases.
-
Functional changes in components/systems
-
Connectivity between components/systems
-
Completeness of backups
-
If OAT is successful
B
Correct answer
Explanation
Heartbeat messages are periodic signals sent between components to verify that communication channels are working and systems are reachable. They specifically test connectivity status rather than functionality, backup completeness, or test success. When heartbeats stop, it indicates a connection failure.
-
test management & control,
-
test specifications & design,
-
test execution & logging,
-
performance & monitoring
B
Correct answer
Explanation
Test data preparation tools support the test specification and design phase by helping create, manage, and prepare the data sets needed for test scenarios. They are not used for test management/control (A), execution/logging (C), or performance monitoring (D), which are separate testing activities.
-
Requires knowledge on the bug fixes and how it affect the system
-
Includes the area of frequent defects
-
Includes the area which has undergone many/recent code changes
-
All of the above
D
Correct answer
Explanation
Effective regression test selection requires multiple considerations: understanding how bug fixes impact system behavior (A), focusing on areas with historical defect patterns (B), and prioritizing recently changed code (C). All three factors are necessary for comprehensive regression coverage.
-
The failure occurs only if you reach a statement taking the TRUE branch of an IF statement, and you got to the statement with a test that passed through the FALSE branch.
-
The failure depends on the program's inability to handle specific data values, rather than on the program's flow of control.
-
Both A and B
-
We are not required to test code that customers are unlikely to execute.
C
Correct answer
Explanation
Complete statement coverage can miss bugs because some defects only occur under specific branch conditions (A), while others depend on data value handling rather than control flow (B). Both scenarios mean a bug can exist even when every statement is executed. Option D is a testing strategy, not a reason for coverage gaps.
-
deviations from standards,
-
requirement defects,
-
design defects,
-
insufficient maintainability and incorrect interface specifications.
-
All of the above.
E
Correct answer
Explanation
Static code reviews excel at finding non-runtime defects such as coding standard deviations, ambiguous requirements, flawed architecture/designs, poor maintainability, and interface mismatches before dynamic execution starts.