Comprehensive Black‑Box Testing Guide for Mobile Apps

Installation, Launch, Uninstall

1. Installation: Verify successful installation on Android (≥2.3) and iOS (≥7.0) on internal memory or SD card, with proper loading indicators and welcome pages. 2. Launch: Test first launch, hot launch, cold launch, forced stop launch, and cache‑clear launch. 3. Uninstall: Ensure normal uninstallation.

Network Testing

1. Network types: 2G, 3G, 4G, Wi‑Fi. 2. Carrier coverage: China Mobile, Unicom, Telecom, virtual carriers. 3. Access points: net and wap. 4. Wi‑Fi variants: open, guest (username/password), fake hotspot, proxy. 5. Weak‑network simulation: test functionality, UI feedback, response time under high latency, packet loss, and fake hotspot conditions. 6. Strong‑network scenarios: login IP changes, large‑volume operations (app upgrades, HTML5 package upgrades, downloads with resume). 7. No‑network: verify UI rendering, data completeness, toast messages. 8. Network switching: various transitions between Wi‑Fi, 2G/3G/4G, and no‑network, including flight mode and dual‑SIM switches. 9. Exception handling: correct error messages, fault tolerance, reconnection, and timeout mechanisms.

Input Field Testing

1. Character fields: full‑width/half‑width English, numbers, spaces, special characters, length boundaries, whitespace handling, multiline input, and security checks for scripts. 2. Numeric fields: boundary values, digit limits, invalid characters, negative numbers, fractions, scientific notation, copy‑paste restrictions, required‑field behavior, and decimal overwrite issues. 3. Date fields: validity of month/day ranges, leap‑year handling, range comparisons, special characters, and copy‑paste security. 4. Duplicate information: uniqueness checks for names/IDs, case sensitivity, and surrounding whitespace handling.

Compatibility Testing

1. OS compatibility: Android ≥2.3, iOS ≥7.0. 2. Brand ROM compatibility: major manufacturers (Huawei, Xiaomi, Meizu, Samsung, OPPO, Vivo, Apple). 3. Resolution compatibility: various screen sizes. 4. Data compatibility across versions. 5. Strategy: prioritize high‑share devices from market rankings, focus on problematic versions/ROMs, and pay special attention to low‑version devices that may crash.

Phone Storage (RAM/Space) Testing

1. No SD card: storage prompts. 2. SD card present but no space: prompts. 3. Internal SD card storage correctness. 4. External SD card storage correctness. 5. Removal of SD card while in use: prompts and behavior. 6. Deleting SD‑card content and subsequent download operations.

Interruptions & Resource Conflict Testing

1. Interruption tests: UI overlay recovery, phone calls, SMS, alarms, calendar, Bluetooth, data‑line/earphone plug‑in/out, standby, lock screen, volume keys, backgrounding, forced close, low‑battery alerts. 2. Interaction tests: audio resource contention, camera/video usage, multiple page windows switching, memory usage.

Upgrade‑Related Testing

1. Data retention on upgrade (full install). 2. Preservation of user settings. 3. Removal of deprecated features. 4. Functional verification after upgrade. 5. Cross‑channel package upgrades. 6. Large version‑gap upgrades. 7. Update prompts for new versions, both optional and mandatory, including cancelation behavior and repeat prompts. 8. Network interruption during upgrade: support for resume or re‑download.

UI Friendliness Testing

1. Consistent style, color, and layout. 2. Correct number of UI elements (e.g., buttons). 3. Accurate tooltip and error messages. 4. Alignment with common user habits. 5. Control alignment, editable date pickers, scrollbars for long text, Tab navigation order, proper rendering during scrolling, absence of redundant buttons/labels, confirmation dialogs for risky actions, and correct control hints.

Screen Rotation Testing

Test G‑sensor‑driven portrait/landscape switches, ensuring UI reloads correctly, memory release, and consistent display after multiple rotations.

Other Tests

Multi‑touch: simultaneous taps on different buttons should not cause UI anomalies or crashes. Single‑point rapid clicks: verify no duplicate requests are generated.

Overall, these black‑box test cases provide a reusable checklist for comprehensive mobile app quality assurance.