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
-
reducing test time
-
no change
-
increase test time
-
can't say
A
Correct answer
Explanation
Higher-quality development methods (like code reviews, static analysis, test-driven development) prevent defects from entering the code in the first place. Fewer defects mean less time spent finding, reporting, and retesting bugs during formal testing phases. Prevention is cheaper than detection.
-
the higher the risk, the earlier the test coverage
-
the lower the risk, the earlier the test coverage
-
Both the above
-
None of the above
A
Correct answer
Explanation
Risk-based testing prioritizes testing efforts based on the level of risk associated with each feature or requirement. Higher-risk areas require more thorough and earlier testing to mitigate potential failures. Option A correctly states that higher risk items receive earlier test coverage, which is the fundamental principle of risk-based testing.
-
Only once at the beginning of the test phase
-
Only once at the end of the test phase
-
Only Once at the end of project closure
-
As detailed in test strategy & ad-hoc basis where needed
D
Correct answer
Explanation
In Risk-Based Testing (RBT), risk identification is an ongoing process that occurs throughout the lifecycle. It is defined in the initial test strategy and continuously performed on an ad-hoc basis as new risks emerge. Distractors stating it occurs only once are incorrect.
-
Impact * Probability of failure
-
Impact * Solution
-
Impact * Requirement
-
Impact * Test level
A
Correct answer
Explanation
Risk level is calculated by multiplying the impact of failure by the probability of failure. This formula Risk = Impact × Probability is standard in risk assessment methodologies. Option A correctly states this calculation, while other options incorrectly multiply impact with unrelated factors like Solution, Requirement, or Test level.
-
a) Breadth Test and Depth Test
-
b) Retesting
-
c) Confirmation Testing
-
d) Sanity Testing
A
Correct answer
Explanation
Maintenance Testing uses two main methodologies: Breadth Testing (testing all affected areas broadly) and Depth Testing (deep testing of specific changed areas). Options b, c, and d describe other testing types but not the specific methodologies for maintenance testing. Option A correctly identifies the two primary approaches used when maintaining existing software.
-
a) ii is true and i,iii,iv are false
-
b) i,iii,iv are true and ii is false
-
c) i,iii,iv are false and ii is true
-
d) iii is true and i,ii,iv are false
B
Correct answer
Explanation
Formal reviews require participants to prepare materials in advance, making statement ii false. The review is led by a trained moderator who is not the author (i true), follows a formal process for follow-up actions (iii true), and its primary goal is defect detection (iv true).
-
a) Structural Testing
-
b) Design Based Testing
-
c) Error Guessing Technique
-
d) Experience Based Technique
A
Correct answer
Explanation
White box testing evaluates the internal structure and code of software, which is why it is called structural testing. Error guessing and experience-based testing are black-box, non-structural techniques.
-
a) Security Testing
-
b) Recovery Testing
-
c) Performance Testing
-
d) Functionality Testing
A
Correct answer
Explanation
Security testing focuses on uncovering vulnerabilities in the system that could be exploited by malicious actors, including viruses and other external threats. Recovery testing verifies system restoration after failures, performance testing measures responsiveness under load, and functionality testing checks if features meet requirements without addressing security concerns.
-
a) Checking test logs against the exit criteria specified in test planning.
-
b) Logging the outcome of test execution.
-
c) Assessing if more tests are needed.
-
d) Writing a test summary report for stakeholders.
B
Correct answer
Explanation
Logging the outcome of test execution is part of the test execution phase, not exit criteria evaluation. Exit criteria tasks include assessing test logs against plans, deciding if more tests are needed, and writing summary reports.
-
a) Load Testing
-
b) Integration Testing
-
c) System Testing
-
d) Usability Testing
A
Correct answer
Explanation
Load testing evaluates how a system performs under different workload conditions, measuring response times, throughput rates, and resource utilization. The goal is to determine if the system can handle expected and peak loads while maintaining proper functionality, which directly matches the description of subjecting the target to varying workloads.
-
a) System Level Testing
-
b) Integration Level Testing
-
c) Unit Level Testing
-
d) Component Testing
B
Correct answer
Explanation
Integration testing specifically focuses on detecting defects in the interfaces and interactions between integrated components. Unit testing examines individual components, while system testing checks the entire integrated system.
-
a) The analysis of batch programs.
-
b) The reviewing of test plans.
-
c) The analysis of program code.
-
d) The use of black box testing
C
Correct answer
Explanation
Static analysis examines source code or compiled code without running the program to identify defects, security vulnerabilities, and coding standard violations. It's performed on the code itself, not on test plans or through black box execution techniques, making 'analysis of program code' the accurate description.
-
a) requirements
-
b) documentation
-
c) test cases
-
d) improvements suggested by users
D
Correct answer
Explanation
Incidents document deviations between expected and actual behavior during testing. Requirements, documentation, and test cases can all contain defects that cause incidents. User suggestions are enhancement ideas rather than failures, so they don't warrant incident reports; they should be captured as change requests or enhancement proposals instead.
-
Java Profiler
-
Testing tool
-
IDE
-
None
A
Correct answer
Explanation
JProbe is a specialized Java suite used for profiling runtime performance, memory usage, threads, and code coverage. It is not an IDE (like Eclipse or IntelliJ) or a general functional testing tool, making the Java Profiler option the correct choice.
-
Analysis Engine, JProbe Connection Manager, JProbe Console
-
Jprobe Editor, JProbe Profiler, Jprobe Engine
-
Jprobe Analysis Engine, probe Thread analyzer
-
Jprobe Analyzer, Jprobe Console
A
Correct answer
Explanation
JProbe's architecture consists of three main components: the Analysis Engine (which does the profiling work), the JProbe Connection Manager (handles communication between profiler and JVM), and the JProbe Console (the UI for viewing results). Options B and C invent non-existent components, and D is incomplete.