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
-
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.
-
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.
-
functional automation tools
-
performance testing tools
-
configuration management tools
-
none of the above.
C
Correct answer
Explanation
ChangeMan and ClearCase are configuration management and version control tools used to track changes, manage versions, and control access to code and artifacts. They are not functional automation tools (A), performance testing tools (B), or unrelated to testing.
-
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.
-
Test case
-
Repository
-
Load test
-
Defects
B
Correct answer
Explanation
The mail functionality in QC (Quality Center) is called a Repository because it stores and manages test artifacts, requirements, and defects in a centralized location. A repository serves as a single source of truth for all testing assets.
-
Smoke & Integration
-
Smoke & Automated
-
Integration & Manual
-
Manual & Automated
D
Correct answer
Explanation
Test sets in Quality Center can contain both manual and automated tests, giving teams flexibility to group different test types together for execution cycles.
-
a folder of test result
-
a folder of testing cycle
-
a group of tests to achieve goal
-
a group of test assigned to a release
C
Correct answer
Explanation
A test set is a logical collection of tests grouped to achieve a specific testing objective or goal, such as validating a feature or supporting a release cycle.
-
hierarchical relationship between requirement
-
The number of test plan needed for each requirement
-
Identify defects that are associated with each requirement
-
Which release and or cycles are linked to each requirement
A
Correct answer
Explanation
The requirement tree defines the hierarchical structure and relationships between requirements, showing how parent and child requirements are organized.
-
Defect
-
Release
-
Dashboard
-
Requirement
B
Correct answer
Explanation
The testing workflow in Quality Center begins with the Release module, where release cycles are created and the overall testing schedule is defined.
A
Correct answer
Explanation
When defects are exported from Quality Center, they are saved as Excel (.xls) files, which can be opened in spreadsheet applications for further analysis.
-
Priority
-
Severity
-
Life cycle
-
User assigned
C
Correct answer
Explanation
Assigning a status to a defect (New, Open, Fixed, Closed, etc.) tracks its progression through the defect life cycle, recording its current state in the workflow.
-
Defect
-
Requirement & Defect
-
Requirement, Test Plan, Defect
-
Requirement, Test Plan, Test lab, Defect
D
Correct answer
Explanation
Defects can be logged from multiple modules - Requirements (during specification review), Test Plan (during test design), Test Lab (during test execution), and the Defect module itself.
-
Audit tab in the Defect module
-
Status column in defect grid
-
History tab in the Defect module
-
Summary column in the Defect grid
C
Correct answer
Explanation
The History tab in the Defect module maintains a complete audit trail of all changes made to a defect, including status updates, field modifications, and comments.