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, hardware configurations, and network conditions.
In mobile app manual testing, testers focus on:
- User experience and usability
- Real-world device behavior
- OS and device compatibility
- Network and performance issues
- Accurate bug reporting
Even in automation-driven projects, manual mobile testing remains critical because many real-world issues (gesture behavior, UI glitches, interruptions) cannot be fully automated.
2. Types of Mobile Testing
1. Functional Mobile Testing
Validates whether the app behaves as per business requirements.
Examples:
- Login and registration
- Navigation and gestures
- Payments and subscriptions
- Push notifications
- Permission handling
2. Performance Mobile Testing
Checks how the app behaves under different usage conditions.
Key areas:
- App launch time
- Memory usage
- CPU utilization
- Battery drain
- Network response time
3. Security Mobile Testing
Ensures user data and APIs are protected.
Includes:
- Authentication and authorization
- Secure API communication
- Data encryption
- Session handling
4. Compatibility Mobile Testing
Validates app behavior across:
- Multiple devices
- OS versions
- Screen sizes
- Manufacturer customizations
3. Mobile App Manual Testing Interview Questions (Beginner → Advanced)
Q1. What is mobile app manual testing?
Answer:
Mobile app manual testing is the process of manually validating a mobile application’s functionality, usability, performance, and security on real devices without using automation tools.
Q2. Why is manual testing important in mobile apps?
Answer:
Because many real-world scenarios like gestures, interruptions, usability issues, and device-specific problems are best identified through manual testing.
Q3. Difference between mobile manual testing and web testing?
Answer:
| Mobile Manual Testing | Web Testing |
| Touch gestures | Mouse & keyboard |
| OS-dependent | Browser-dependent |
| Hardware interaction | Minimal hardware |
| Network variability | Relatively stable |
Q4. What types of mobile apps exist?
Answer:
- Native apps: Built for Android or iOS
- Hybrid apps: Web apps inside native container
- 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 simultaneously, especially common in Android.
Q6. How does OS fragmentation affect manual testing?
Answer:
- UI inconsistencies
- Device-specific bugs
- Performance variations
- Increased test coverage requirements
4. Real Device Testing in Manual Mobile Testing
Q7. Why is real device testing important?
Answer:
Real devices expose issues that emulators cannot:
- Battery drain
- Network interruptions
- Touch sensitivity issues
- OEM-specific behavior
Q8. Emulator vs real device testing?
Answer:
| Emulator | Real Device |
| Faster & cheaper | Real-world accuracy |
| Limited hardware | Real sensors & battery |
| Good for early checks | Mandatory before release |
Q9. What scenarios should always be tested on real devices?
Answer:
- Incoming calls & notifications
- Low battery and power-saving mode
- Network switching
- App background and foreground behavior
5. Android vs iOS Manual Testing – Scenario-Based Questions
Android Manual Testing Challenges
- High OS fragmentation
- Multiple manufacturers
- Different screen sizes
- OEM customizations
iOS Manual Testing Challenges
- Strict permission prompts
- Background execution limits
- App Store compliance rules
Q10. Key differences between Android and iOS manual testing?
Answer:
Android testing focuses on device and OS compatibility, while iOS testing focuses on lifecycle control and permissions.
Q11. Android activity lifecycle?
Answer:
onCreate → onStart → onResume → onPause → onStop → onDestroy
Q12. iOS application lifecycle states?
Answer:
Not Running → Inactive → Active → Background → Suspended
6. Network & Connectivity Testing (Manual Perspective)
Q13. How do you manually test poor network conditions?
Answer:
- Switch between Wi-Fi and mobile data
- Enable airplane mode
- Test with slow or unstable networks
Q14. What is network switching testing?
Answer:
Validating app stability when the network changes during an active transaction.
Q15. How do you test offline mode?
Answer:
- Disable network
- Perform user actions
- Re-enable network and verify data sync
7. Appium Awareness for Manual Testers
Manual testers are not expected to write complex automation, but basic awareness is expected.
Q16. What is Appium?
Answer:
Appium is an open-source mobile automation framework used to automate Android and iOS applications.
Q17. Why should a manual tester know Appium basics?
Answer:
To:
- Design automation-friendly test cases
- Collaborate effectively with automation teams
- Understand automation limitations
Sample Appium Locator Examples
AppiumBy.id(“loginBtn”)
AppiumBy.accessibilityId(“username”)
8. ADB Commands – Useful for Manual Testers
List connected devices
adb devices
Install APK
adb install app.apk
Capture logs
adb logcat
Clear app data
adb shell pm clear com.example.app
Q18. Why should manual testers know ADB commands?
Answer:
ADB helps in capturing logs, reproducing crashes, resetting app state, and validating background behavior.
9. Mobile App Manual Test Case Examples
Login Feature Test Cases
- Valid credentials
- Invalid credentials
- Account lock after failed attempts
- Biometric authentication
- Network loss during login
E-commerce App Test Cases
- Add product to cart
- Apply coupon
- Payment interruption
- Order retry
- Inventory update validation
OTT App Test Cases
- Video playback
- Resume after interruption
- Screen rotation handling
- Background playback
- DRM validation
10. Bug Reporting Format (Manual Testing Focus)
Sample Defect Report
Title: App crashes when switching network during checkout
Environment: Android 13, Samsung S22
Steps to Reproduce:
- Launch app
- Add item to cart
- Proceed to payment
- Switch from Wi-Fi to mobile data
Expected Result: Payment retries
Actual Result: App crashes
Logs: Attached
Severity: Critical
11. Performance Profiling & Crash Analysis (Manual View)
Q19. How do you identify performance issues manually?
Answer:
- Slow screen loading
- UI freezes
- App lag during navigation
- Increased battery drain
Q20. What is ANR?
Answer:
ANR (Application Not Responding) occurs when the UI thread is blocked for too long.
Q21. How do you identify memory leak symptoms manually?
Answer:
- App slows down over time
- Frequent crashes
- Increased battery consumption
Q22. How do you analyze crashes?
Answer:
- Review logs
- Check reproduction steps
- Identify device/OS patterns
12. Security Testing & API Authentication (Manual)
Q23. What security checks are done in manual mobile testing?
Answer:
- Secure login/logout
- Session timeout validation
- Data masking
- Permission misuse checks
Q24. How do you test API authentication manually?
Answer:
- Invalid credentials
- Expired sessions
- Logout and token invalidation
Q25. 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
Q26. How do you prioritize test cases in manual testing?
Answer:
By focusing on:
- Business-critical flows
- High-risk features
- Frequently used scenarios
Q27. How do you handle device-specific bugs?
Answer:
- Reproduce on similar devices
- Analyze OS and hardware differences
- Attach logs and screenshots
Q28. How do you handle production defects?
Answer:
- Reproduce quickly
- Analyze logs
- Provide RCA
- Suggest preventive test cases
14. Quick Revision Sheet (Cheat Sheet)
- Focus on real devices
- Handle OS fragmentation
- Test network switching
- Understand Android vs iOS differences
- Know basic ADB & Appium
- Write clear, reproducible bugs
15. FAQs – Mobile App Manual Testing Interview Questions
Q1. Is manual testing still relevant in mobile apps?
Yes, it is critical for usability, exploratory, and real-world scenarios.
Q2. Is automation mandatory for manual testers?
Basic awareness is expected, not expert-level scripting.
Q3. What do interviewers focus on most?
Real device scenarios, bug quality, and practical testing approach.