NEW
Font size
WorksheetsSoftware Testing MCQs
Total questions: 59
Worksheet time: 30mins
Which principle of testing says defects are often concentrated in a few modules?
Absence-of-errors fallacy
Pesticide paradox
Defect clustering
Early testing
Running the same test cases repeatedly will find fewer new bugs. This is called:
Defect clustering
Pesticide paradox
Early testing
Exhaustive testing
Even if software is error-free, it may still fail to meet user needs. This refers to:
Exhaustive testing
Absence-of-errors fallacy
Defect clustering
Context-dependent principle
Early testing is important because:
Prevents regression
Improves UI
Fixing defects early is cheaper
Increases complexity
Which principle states exhaustive testing is impossible?
Complete testing is not feasible
Defect clustering
Pesticide paradox
Absence-of-errors fallacy
Verification checks if the product is built ___, Validation checks if the right product is built.
Incorrectly
Correctly
Slowly
With bugs
Which activity is part of validation?
Code walkthrough
User Acceptance Testing
Static review
Code inspection
Which is part of verification?
Reviews and walkthroughs
Beta testing
System testing
Alpha testing
Validation ensures:
Product follows standards
Product meets user requirements
Code is fully covered
Bugs are fixed
Verification is usually done by:
Developers and testers internally
End-users
Customers
Operators
Static testing means:
Running code
Reviewing without execution
Beta testing
Smoke testing
Walkthroughs are usually led by:
Moderator
Author
Recorder
Reviewer
Which role records defects during inspections?
Moderator
Recorder
Reviewer
Author
Which is a formal static technique using checklists?
Walkthrough
Inspection
Exploratory testing
Regression
Which of these is NOT a static testing technique?
Review
Walkthrough
Regression testing
Inspection
Unit Testing focuses on:
Individual modules
Entire system
User acceptance
Integration
Integration Testing focuses on:
Individual functions
Interaction between modules
Database queries only
Hardware testing
System Testing ensures:
End-to-end system functionality
Only unit-level bugs
Only UI responsiveness
Only stress load
Acceptance Testing validates:
Code logic
Load handling
Customer requirements
Regression defects
Alpha testing is done at:
Developer’s site by internal users
Customer site
Real-world users only
Vendors
Beta testing is done at:
Developer site
Customer environment by real users
Design stage
With stubs
Equivalence Partitioning divides inputs into:
Statements
Classes expected to behave similarly
Loops
Branches
Boundary Value Analysis tests:
Random values
Edge values of input ranges
Midpoints only
Paths
Decision Table Testing is useful for:
Simple inputs
Multiple condition-based outcomes
Loops
Regression
State Transition Testing is useful when:
No states exist
System behavior depends on past states
Code is simple
Only loops exist
Error Guessing relies on:
Decision tables
Automated tools
Tester’s intuition/experience
Formal reviews
Which is NOT a black-box technique?
Equivalence Partitioning
Boundary Value Analysis
State Transition Testing
Statement Coverage
Boundary Value Analysis requires testing at:
Just below, at, and just above boundaries
Only valid inputs
Only invalid inputs
Middle range
Decision Table Testing is especially strong for:
GUI checks
Business rules
Loop testing
Path testing
Statement coverage ensures:
Every line of code executes at least once
Every condition is tested
Every loop runs once
All paths executed
Branch coverage ensures:
Each decision outcome (true/false) is executed
All loops covered
Only boundaries tested
All inputs tested
Path coverage ensures:
Only simple paths
All independent paths executed
Only boundary paths
Random paths
Loop testing ensures:
Branches tested
Different loop iterations validated
All paths
Boundaries
Which is strongest coverage criterion?
Statement
Branch
Path
Loop
Which is NOT white-box?
Branch coverage
Statement coverage
Path coverage
Boundary value analysis
Big Bang integration means:
All modules combined and tested at once
Top-down
Bottom-up
Regression only
Top-down integration uses:
Stubs
Drivers
Beta tests
Scripts
Bottom-up integration uses:
Stubs
Drivers
Checklists
Regression
Main drawback of Big Bang approach is:
Easier defect detection
Hard to isolate bugs
Early prototype available
Saves cost
Regression Testing ensures:
Changes don’t break existing functionality
Only new features tested
Database tests
Load tested
Smoke Testing is used to:
Check basic system stability quickly
Perform stress tests
Execute all cases
Debug loops
Stress Testing evaluates:
System under extreme load
User acceptance
Code complexity
Boundaries
Ad-hoc Testing is done:
With full planning
Without formal plan
Only automated
Only by customers
Exploratory Testing means:
Simultaneous learning, designing, and executing tests
Using regression
Using path coverage
Using stubs
Compatibility Testing ensures:
All modules integrate
Code follows standards
Software works on different platforms/browsers
Regression only
Acceptance testing is also called:
Validation testing
Verification testing
Static testing
Stress testing
Alpha and Beta testing are types of:
Regression
Unit testing
Acceptance testing
Integration testing
Cyclomatic complexity measures:
Number of independent paths
Lines of code
Functions
Defects
Formula for cyclomatic complexity is:
N - E + P
E - N + 2P
E + N - P
N + P - E
High cyclomatic complexity indicates:
Hard-to-test code
Easier maintenance
Bug-free code
Low defects
Defect density =
Defects per KLOC (thousand lines of code)
Defects per module
Defects per tester
Defects per customer
Defect turnaround time measures:
Bug severity
Time to fix a bug
Density of bugs
Cost of bug
Which metric reflects test completeness?
Defect turnaround
Test coverage
Defect density
Cyclomatic complexity
The V-Model shows:
Testing activities mapped to development phases
Only coding process
Deployment only
Maintenance
Agile Testing principle is:
Continuous testing during development
Test after release
Regression only
Code-only focus
ISO 9000 relates to:
Quality management systems
Functional testing
Bug detection
Regression
CMMI Level 2 is:
Repeatable process
Initial
Defined
Optimizing
CMMI Level 3 is:
Repeatable
Defined process
Initial
Managed
CMMI Level 5 is:
Repeatable
Defined
Managed
Optimizing
