Font size
WorksheetsUNIT-III: LEVELS OF TESTING (50 MCQs)
Total questions: 100
Worksheet time: 50mins
Levels of testing are required to:
Reduce cost
Identify defects at different stages
Improve UI only
Delay development
Unit testing is performed on:
Complete system
Individual components
Database only
End users
Unit testing is mainly done by:
End user
Developer
Customer
Tester only
A class is treated as a testable unit in:
Java / OOP applications
Web development only
Hardware testing
Beta testing
Unit test planning is done during:
Integration phase
Coding phase
A test harness is:
Data storage
A collection of tools to support unit testing
A compiler
Customer environment
Unit testing helps detect:
System failures
Logic and coding errors
UI design issues
Security threats only
Integration testing verifies:
Individual components
Interaction between integrated modules
Application performance
Database design
Top-down integration testing uses:
Drivers
Stubs
Compilers
Automated scripts only
Bottom-up integration testing uses:
Stubs
Drivers
System testing is done to test:
Small units
Entire software system
A single class
Only GUI
Regression testing ensures:
Unchanged modules still work after modifications
Only new features work
System shuts down properly
Installation success
Alpha testing is done at:
Customer site
Developer site
Live production
Remote testing
Beta testing is performed at:
Developer site
User environment
Testing lab
Server room
Acceptance testing ensures:
Code quality
Software meets user requirements
Unit tests should be:
Complex
Repeatable and simple
Manual only
Unpredictable
Smoke testing is also known as:
Sanity testing
Build verification testing
Load testing
Debug testing
Sanity testing is performed after:
Major release
Minor changes or fixes
Documentation
UI completion
Functional testing belongs to:
System testing
Integration testing
Acceptance testing
All of the above
Non-functional testing includes:
Performance testing
Boundary testing
Load testing is done to check:
Structural design
System performance under expected load
UI screens
Security
Stress testing verifies:
Stability under extreme conditions
Minor functional errors
Documentation
Hardware parts
Compatibility testing ensures:
System runs on different environments
Only functional accuracy
Database backup
Hardware stability
Usability testing focuses on:
Code structure
User experience
Database performance
Network reliability
Security testing ensures:
UI looks good
System protects data and prevents unauthorized access
A test report for unit testing includes:
Execution status
Code screenshot
Login credentials
Marketing plan
Test data preparation is part of:
Debugging
Test execution
Test planning
System deployment
Regression testing is triggered by:
Code changes
New feature development
Bug fix
All of the above
Integration test planning must consider:
Testing sequence
Module dependency
Stubs and drivers
All of the above
Record and replay tools are useful in:
Unit testing
Regression testing
Testing begins with:
Unit testing
System testing
Beta testing
Acceptance testing
Black-box techniques are mainly used in:
Unit testing
System testing
Acceptance testing
Both b and c
White-box techniques are mainly used in:
Unit testing
Integration testing
System testing
Beta testing
Integration strategies include:
Big-bang
Top-down
Bottom-up
All of the above
Big-bang integration testing disadvantage:
Easier to test
Difficult to isolate defects
Test automation is more useful in:
One-time tests
Regression testing
Beta testing
Documentation
End-to-end testing verifies:
Small modules
Complete workflow
Debug logs
Sample outputs
Recovery testing checks:
Restart capability after failure
Speed
UI color
Installation
Volume testing examines performance with:
Low data
Very large data
No data
Sample data
Keyword-driven testing belongs to:
Manual testing
Automation framework
Unit tests must include:
Test data
Expected output
Inputs and execution steps
All of the above
System test types include:
Functional
Non-functional
Regression
All of the above
Acceptance testing is usually conducted by:
Developers
Customers or end users
Security professionals
Maintenance team
Alpha testing comes before:
Unit testing
Beta testing
Integration
Requirements
A build that fails smoke testing is:
Accepted
Rejected
Sanity testing checks:
Minor fixes
Full functionality
Production environment only
Documentation
System testing environment should be:
Very different from user environment
Similar to production environment
Local laptop only
No environment required
Pilot testing is similar to:
Load testing
Beta testing
Unit testing
Boundary testing
Smoke testing is done:
Before detailed functional testing
After deployment
During beta stage
After acceptance
Goal of levels of testing is:
Reduce testing
Improve defect detection using multiple stages
Choose the correct option:
Add new feature
Fix critical bug
Delay release
Remove documentation
Test management primarily focuses on
Coding
Planning and controlling testing activities
Writing documentation
Designing UI
Testing and debugging goals must be defined during
Deployment
Test Planning
Maintenance
Coding
Which document defines how testing will be carried out?
SRS
Test Plan
Vision Document
Test Strategy
A test plan is usually prepared by the
Developer
Client
Test Manager
End user
Which of the following is NOT a test plan component?
(a)
Test objectives describe:
What testing will achieve
Who will use the software
Cost of testing
Design patterns
A Test Plan Attachment usually contains:
Test Data
Source Code
User Manuals
Sales Forecast
Locating test items refers to identifying:
Stakeholders
Requirements
The components to be tested
Hardware setup
The final outcome of testing is documented in the:
Bug log
Test report
Risk matrix
Review form
A test result report should be:
Complex
Understandable
Which group creates test policies and procedures?
End users
Management
Operation staff
Customers
The testing specialist group mainly deals with:
Designing UI
Executing tests
Writing business proposals
Marketing strategies
A policy document defines:
Test cases
Rules and guidelines for testing
Coding style
Regression timelines
Testing and debugging are:
Same
Opposites
Complementary
Not related
Debugging is performed by:
Tester
Developer
The role of testing group in planning includes:
Estimating resources
Creating UI mockups
Deployment activities
Database setup
A testing group must possess skills such as:
UX design
Analytical and technical skill
Sales negotiation
Photography
Building a testing group involves:
Hiring and skill development
Removing automation
Stopping training
Changing product features
Which of the following is a part of test policy development?
Test coverage rules
Marketing strategy
UI design guideline
None
Test scheduling includes:
Debug steps
Timeline for activities
A good test plan must be:
Ambiguous
Flexible and clear
Confidential
Very lengthy
Entry and exit criteria define:
Who writes code
When testing starts and stops
Cost of project
Business risks
Risk analysis in test planning helps in:
Increasing product defects
Mitigating issues before testing
Reducing coverage
Removing manual testing
Scope of testing identifies:
What will be tested
What will NOT be tested
Both a and b
Only test schedule
A good test report must include:
Test results and defect statistics
Source code
Traceability matrix is used for:
Linking requirements to test cases
Designing UI
Managing budget
Database mapping
The primary audience for a test report is:
Testers only
Developers and managers
End users
Public
Test metrics help in:
Measuring effectiveness
Debugging
Changing UI
Deployment
Resource planning determines:
Code architecture
Hardware, software, manpower required
User feedback
UI color
Communication in testing must be:
Delayed
Clear and continuous
Test environment setup includes:
Hardware setup
Software installation
Database setup
All of the above
Which group approves the final test strategy?
Test Engineer
Management
Customer
Developer
Test execution is guided by:
Test strategy
Test plan
Both a and b
None
A bug triage meeting is held to:
Write test cases
Prioritize defects
Train new users
Perform acceptance testing
A stable testing team improves:
Defect count
Test consistency and accuracy
Test planning begins during:
Requirement phase
Deployment phase
Maintenance phase
After coding
Test execution schedule defines:
Who will run tests and when
User interface details
Network setup
Business strategy
Test deliverables include:
Test plan
Test scripts
Test report
All of the above
Pilot testing is mainly done during:
Planning
Final acceptance testing
Deployment
Debugging
A skilled testing group reduces:
Test accuracy
Risk of product failure
A review of the test plan ensures:
Proper test coverage
UI consistency
Code formatting
Packaging
Test management tools help in:
Writing code
Tracking test cases and results
Marketing
Billing
Which skill is most important for testers?
Analytical thinking
Drawing
Singing
Cooking
Test policy defines:
High-level test guidelines
Individual test steps
Debug instructions
Code comments
A defect reporting system must track:
Status
Priority
Test control ensures:
Testing stays on schedule
Testers stop reporting bugs
UI is updated
Database is clean
Stakeholders use test reports to:
Approve release decisions
Change UI theme
Write test cases
Debug code
A well-defined testing policy helps in:
Standardizing testing process
Increasing software size
Reducing quality
Avoiding automation
Testing maturity improves when:
Policies and procedures evolve
Tester skill decreases
Communication stops
No documentation exists
