How to Quickly and Accurately Locate Online Bugs: A Practical Guide for Testers
This article outlines a systematic, step‑by‑step approach for testers to gather evidence, reproduce, and diagnose production bugs on mobile and web platforms, emphasizing thorough data collection, environment checks, and collaborative debugging to improve response speed and reliability.
After a long period of silence, the author returns with a commitment to keep publishing technical articles despite a hectic schedule, emphasizing the importance of continuous learning and sharing.
In fast‑paced agile development, rushed releases often lead to low code quality and insufficient testing, resulting in post‑release bugs that pressure testers, product managers, and operations teams. The author stresses staying calm, being open to feedback, and methodically locating and resolving issues.
The guide begins by recommending extensive evidence collection when a bug is reported, encouraging testers to think broadly and consider all possible user scenarios.
When only a textual description is available:
1. Verify user account and related business data to rule out data anomalies. 2. Check logs to understand user actions. 3. Test the main workflow in a test environment. 4. Verify the same workflow in the production environment. 5. Test on both iOS and Android devices. 6. Test across different OS versions. 7. Test different app versions. 8. Test various network conditions (Wi‑Fi, 4G, 2G, weak network). 9. Use intuition and experience to hypothesize causes and attempt reproduction. 10. Consider device settings (location, push notifications, network permissions). 11. Consider large data volumes, long‑running operations, new feature releases, and involve developers for assistance.
When detailed information (environment, phone number, steps, screenshots, video, device model, OS version, app version, network) is provided:
1. Confirm the user’s basic information and related business data. 2. Reproduce the issue repeatedly based on the supplied steps. 3. Analyze screenshots and videos to extract clues such as device type, network, and app version. 4. Recreate the user’s business scenario to trigger the bug. 5. Recognize that many bugs are compatibility issues (different iOS/Android versions, network conditions, device models). 6. Examine API parameters, responses, and related database records for anomalies.
The article ends with a promise to continue the series, followed by a disclaimer and contact information for collaborations: [email protected] .
FunTester
10k followers, 1k articles | completely useless
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.