Manual & Mobile Testing Complete Guide - Kaustubh Gurav
Table of Contents
1. Manual Testing Basics
2. Advanced Manual Testing Concepts
3. Mobile Testing Concepts
4. Test Planning & Closure Activities
1. Manual Testing Basics
Manual Testing is the process of manually checking software for defects. The tester takes over the role of an
end-user and tests the software to find unexpected behavior or bugs.
Key Concepts:
- SDLC (Software Development Life Cycle)
- STLC (Software Testing Life Cycle)
- Types of Testing: Smoke, Sanity, Regression, Retesting, Functional, Non-functional, etc.
- Test Case Design Techniques: BVA, ECP, Decision Table, State Transition, Use Case
- Defect Life Cycle
- Severity vs Priority
- QA vs QC
Sample Interview Q&A:
Q: What is the difference between regression testing and retesting?
A: Regression testing ensures that new code changes have not affected the existing functionalities, whereas
retesting is done to verify the bug fixes.
Q: What are the principles of software testing?
A: Testing shows the presence of defects, exhaustive testing is impossible, early testing saves time and
money, etc.
2. Advanced Manual Testing Concepts
Advanced Concepts:
- Test Plan & Strategy
- Test Coverage & Traceability Matrix (RTM)
- Agile Testing & Scrum Framework
- Defect Tracking Tools: JIRA, Bugzilla
- Exploratory Testing
- Risk-Based Testing
Sample Interview Q&A:
Q: What is RTM?
A: Requirement Traceability Matrix is a document that maps and traces user requirements with test cases.
Q: What is the purpose of a test strategy?
A: It defines the overall testing approach and goals, including scope, objectives, methods, and tools.
3. Mobile Testing Concepts
Mobile Testing includes validating mobile apps on Android and iOS platforms.
Types:
- Functional Testing
- UI/UX Testing
- Compatibility Testing
- Performance Testing
- Interrupt Testing (calls/SMS)
- Installation/Uninstallation Testing
Sample Interview Q&A:
Q: How is mobile testing different from web testing?
A: Mobile testing involves additional factors like device fragmentation, OS versions, battery usage, and touch
gestures.
Q: What are real device and emulator testing?
A: Real devices are physical devices; emulators simulate mobile devices in a virtual environment.
4. Test Planning & Closure Activities
Test Planning Includes:
- Scope and Objective of Testing
- Test Environment Setup
- Resources and Responsibilities
- Risk Analysis
Test Closure Activities:
- Test Summary Report (TSR)
- Defect Analysis and Metrics
- Lessons Learned and Best Practices
Reporting Formats:
- Bug Report Template: ID, Summary, Steps to Reproduce, Severity, Priority, Status
- Test Case Template: TC ID, Description, Precondition, Steps, Expected Result, Actual Result, Status
Sample Interview Q&A:
Q: What is included in a test summary report?
A: Total test cases executed, passed/failed, defect count, severity distribution, pending defects, conclusion.
