APP Fault Reproduction Using Key Logs and UI Screenshot Comparison
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current APP development processes face challenges in capturing logs when the development and debugging tool is disconnected or the APP crashes, leading to inefficient and inaccurate fault reproduction and root cause location.
Innovation Solution
An APP testing method that directly captures key logs from terminal equipment, analyzes them to determine fault causes, and compares UI screenshots with pre-stored designs to identify differences, enabling quick fault reproduction and accurate location without relying on a development tool.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If a development and debugging tool is used to capture logs, then fault reproduction and root cause location can be assisted, but the process becomes dependent on the tool connection and loses flexibility
Solution Approach 1:
The terminal device performs self-diagnosis by capturing and analyzing its own logs and screenshots without external tool assistance. The device autonomously monitors itself, captures fault information, and generates test reports independently, eliminating dependency on external development tools while maintaining diagnostic capability
Solution Approach 2:
A test agent is introduced as an intermediary component installed on the terminal device. This agent captures logs and screenshots locally and transmits them to the testing system, serving as a bridge between the terminal and the testing platform. This enables flexible operation without direct tool connection while maintaining data quality for accurate fault analysis
2Loss of information
If traditional log capture methods are used, then fault information can be obtained, but the process is time-consuming and reduces development efficiency
Solution Approach 1:
The system proactively captures logs and screenshots at predetermined time points and stores them locally before faults occur. When a fault is detected, the pre-captured information is immediately available for analysis, eliminating the time delay associated with traditional on-demand log capture methods and significantly improving diagnostic speed
Solution Approach 2:
The terminal device continuously captures and stores logs and screenshots in real-time during operation. This continuous data collection ensures that fault information is always available when needed, eliminating gaps in information that occur with periodic or on-demand capture methods, thereby maintaining high development efficiency
3Measurement precision
If UI screenshots are captured and compared with design drawings, then UI differences can be identified, but the process requires additional processing time
Solution Approach 1:
The manual or mechanical process of visual UI comparison is replaced with automated image processing and pattern recognition algorithms. The system automatically compares captured screenshots with design drawings using computational methods, achieving high-precision UI difference detection without the time-consuming manual review process
Solution Approach 2:
The comparison process utilizes image parameter analysis (such as pixel values, color codes, and structural features) rather than visual inspection. By transforming the UI verification task into a parameter-based computational problem, the system achieves rapid and accurate detection of UI differences, significantly reducing testing time while maintaining high precision
Data Source
AI summary
Provided are an application software (APP) testing method, an electronic device, and a computer-readable storage medium. The APP testing method includes: acquiring a key log; determining information related to a tested fault cause according to the key log; acquiring a User Interface (UI) screenshot; and comparing the UI screenshot with a pre-stored UI design drawing, and determining whether there is a difference between the UI screenshot and the UI design drawing. The APP testing method provided by the present disclosure can realize quick check of network access logs and crash logs even without a platform of a development tool, assist testers and developers in problem reproduction and fault location, and improve development efficiency of the developers.