1. What Is Mobile Testing? (Simple Explanation)
Mobile testing is the process of validating a mobile application to ensure it works correctly on real devices, different operating systems, screen sizes, and network conditions.
In manual mobile testing, testers focus on:
- Real user behavior
- Exploratory scenarios
- UI/UX validation
- Device-specific issues
- Edge cases that automation may miss
Manual mobile testing is critical because real users don’t behave like scripts, and many mobile issues appear only during hands-on usage.
2. Types of Mobile Testing
1. Functional Mobile Testing
Validates whether the app behaves as per business requirements.
Examples:
- Login & signup
- Navigation
- Payments
- Notifications
- App permissions
2. Performance Mobile Testing
Checks how the app behaves under stress.
Focus areas:
- App launch time
- Memory usage
- CPU usage
- Battery consumption
- Network response time
3. Security Mobile Testing
Ensures data safety and secure access.
Includes:
- Authentication & authorization
- Secure API calls
- Data encryption
- Local storage security
4. Compatibility Mobile Testing
Ensures smooth behavior across:
- Devices
- OS versions
- Screen sizes
- Manufacturers
3. Manual Mobile Testing Interview Questions (Beginner → Advanced)
Q1. What is manual mobile testing?
Answer:
Manual mobile testing is the process of validating mobile applications manually on real devices to identify functional, usability, performance, and compatibility issues.
Q2. Why is manual mobile testing still important?
Answer:
Because manual testing helps uncover:
- UI/UX issues
- Exploratory bugs
- Real user behavior problems
- Device-specific issues
Q3. Difference between manual mobile testing and automation?
Answer:
| Manual Mobile Testing | Automation Testing |
| Human interaction | Script-driven |
| Exploratory & usability | Regression & repetition |
| Slower execution | Faster execution |
| Flexible | Predefined logic |
Q4. What are native, hybrid, and mobile web apps?
Answer:
- Native apps: Built for Android or iOS
- Hybrid apps: Web apps inside native wrapper
- Mobile web apps: Run in mobile browsers
Q5. What is OS fragmentation?
Answer:
OS fragmentation refers to multiple OS versions and device models being used at the same time, especially common in Android.
4. Real Device Testing Interview Questions
Q6. Why is real device testing important in manual mobile testing?
Answer:
Because emulators/simulators cannot accurately replicate:
- Battery drain
- Network interruptions
- Sensor behavior
- Touch sensitivity
- Thermal issues
Q7. Emulator vs real device testing?
Answer:
| Emulator | Real Device |
| Faster & cheaper | Accurate behavior |
| Limited hardware | Real sensors |
| Good for early testing | Mandatory before release |
Q8. What scenarios must be tested on real devices?
Answer:
- Incoming calls
- SMS & notifications
- Low battery
- Network switching
- App background/foreground
5. Android vs iOS Manual Testing – Interview Focus
Android Testing Characteristics
- Multiple manufacturers
- High OS fragmentation
- APK installation
- Flexible background services
iOS Testing Characteristics
- Limited device models
- Controlled ecosystem
- IPA installation
- Strict background execution
Q9. Key challenges in Android vs iOS testing?
Answer:
Android testing focuses on device diversity, while iOS testing focuses on platform restrictions and permissions.
Q10. Android activity lifecycle?
Answer:
onCreate → onStart → onResume → onPause → onStop → onDestroy
Q11. iOS application lifecycle?
Answer:
Not Running → Inactive → Active → Background → Suspended
6. Network & Connectivity Testing Questions
Q12. How do you test app behavior on poor networks?
Answer:
- Switch between Wi-Fi and mobile data
- Enable airplane mode
- Use network throttling tools
Q13. What is network switching testing?
Answer:
Validating app behavior when network changes during an active transaction.
Q14. How do you test offline mode manually?
Answer:
- Disable network
- Perform user actions
- Re-enable network and verify sync
7. Manual Testing Awareness of Appium & Automation
Interviewers expect manual testers to understand automation basics, even if they don’t write scripts daily.
Q15. What is Appium?
Answer:
Appium is an open-source mobile automation framework used to automate Android and iOS apps.
Q16. Why should manual testers know Appium basics?
Answer:
To:
- Collaborate with automation teams
- Design automation-friendly test cases
- Understand automation limitations
Sample Appium locator awareness
driver.findElement(AppiumBy.id(“loginBtn”)).click();
8. ADB Commands – Must-Know for Manual Testers
Check connected devices
adb devices
Install APK
adb install app.apk
Capture logs
adb logcat
Clear app data
adb shell pm clear com.example.app
Toggle Wi-Fi
adb shell svc wifi disable
adb shell svc wifi enable
Q17. Why are ADB commands important for manual testers?
Answer:
They help with:
- Log analysis
- Debugging crashes
- Network simulation
- App state reset
9. Manual Mobile Test Case Examples
Login Feature Test Cases
- Valid credentials
- Invalid credentials
- Account lock
- Biometric login
- Network loss during login
E-commerce App Test Cases
- Add item to cart
- Apply coupon
- Payment failure
- Order retry
- Inventory update
OTT App Test Cases
- Video buffering
- Resume playback
- Screen rotation
- Background playback
- DRM validation
10. Bug Reporting Format (Manual Mobile Testing)
Sample Defect Report
Title: App crashes on rotation during video playback
Environment: Android 13, Samsung S22
Steps to Reproduce:
- Launch app
- Play video
- Rotate device
Expected Result: Video continues playing
Actual Result: App crashes
Logs: Logcat attached
Severity: Critical
11. Performance Profiling & Crash Analysis Questions
Q18. How do you identify memory leaks manually?
Answer:
- Repeated navigation testing
- Monitoring app slowdown
- Using Android Profiler or Xcode Instruments
Q19. What is ANR?
Answer:
ANR (Application Not Responding) occurs when the UI thread is blocked for too long.
Q20. Performance metrics to monitor?
Answer:
- App launch time
- Memory usage
- CPU usage
- Battery drain
- FPS
Q21. How do you analyze app crashes?
Answer:
- Logcat
- Stack traces
- Crash analytics tools
12. Security Testing & API Auth Questions (Manual Focus)
Q22. What security checks are done in manual mobile testing?
Answer:
- Secure local storage
- Encrypted API calls
- Session handling
- Logout behavior
Q23. How do you test API authentication manually?
Answer:
- Invalid token
- Expired token
- Missing authorization headers
Q24. What is data leakage testing?
Answer:
Ensuring sensitive data is not exposed in logs, cache, screenshots, or local storage.
13. Advanced Manual Mobile Testing Interview Questions
Q25. How do you handle flaky mobile issues?
Answer:
- Reproduce on multiple devices
- Check network and OS versions
- Collect logs and screenshots
Q26. How do you test background & foreground behavior?
Answer:
- Minimize app
- Switch apps
- Return to app and validate state
Q27. How do you test memory pressure scenarios?
Answer:
- Use multiple apps simultaneously
- Observe app behavior under low memory
14. Quick Revision Sheet (Cheat Sheet)
- Prefer real device testing
- Test network switching
- Handle OS fragmentation
- Monitor memory & battery
- Capture logs
- Write clear defect reports
15. FAQs – Manual Mobile Testing Interview Questions
Q1. Is manual mobile testing still relevant?
Yes, especially for usability and exploratory testing.
Q2. Should manual testers learn automation?
Basic knowledge is highly recommended.
Q3. Android or iOS – which is harder to test manually?
Android due to device and OS fragmentation.