# US 2024/0394174 A1 · Application software testing method, electronic device and computer-readable storage medium

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0394174 A1
- Document ID: US20240394174A1
- Status: Published application
- Kind: A1
- Application number: 18/273,265
- Filed: 2022-07-18
- Published: 2024-11-28
- Earliest claimed: 2022-03-22
- Assignees: Crsc Institute of Smart City Research & Design
- Applicants: Crsc Institute of Smart City Research &Design
- Inventors: Jing LUO; Jianzheng DUN; Pei ZHANG; Xin HOU; Zijian LI
- Web page: https://patentgrep.com/patent/US20240394174A1

## CPC

- G06F 11/3698: Environments for analysis, debugging or testing of software
- G06F 11/3688: {for test execution, e.g. scheduling of test suites}
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F 11/3438: {monitoring of user actions (tracking the activity of the user H04L67/535)}
- G06F 11/3676: {for coverage analysis}
- G06F 11/3692: {for test results analysis}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

The present disclosure provides 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.

## Claims

### Claim 1

An application software (APP) testing method, comprising:
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.

### Claim 2 (depends on 1)

The APP testing method of claim 1, wherein the key log comprises a network request log and/or an exception log.

### Claim 3 (depends on 1)

The APP testing method of claim 1, wherein
acquiring the key log comprises:
storing an interface request in a network request log and return data for the interface request in an interceptor;
determining the information related to the tested fault cause according to the key log comprises:
analyzing the interface request and the return data in the interceptor, and caching an analysis result; and
highlighting the information related to the tested fault cause in the analysis result.

### Claim 4 (depends on 3)

The APP testing method of claim 3, wherein highlighting the information related to the tested fault cause in the analysis result comprises:
displaying a list of network request logs according to the analysis result;
determining a network request log related to the tested fault cause according to a response code of each network request in the analysis result; and
displaying the network request log related to the tested fault cause in a corresponding font color.

### Claim 5 (depends on 1)

The APP testing method of claim 1, wherein
acquiring the key log comprises:
acquiring an exception log in response to a system exception, wherein the system exception comprises a crash and/or an operation exception; and
storing the exception log in an exception log file;
determining the information related to the tested fault cause according to the key log comprises:
reading the exception log file, and determining the exception log related to the system exception; and
highlighting the exception log related to the system exception.

### Claim 6 (depends on 1)

The APP testing method of claim 1, wherein acquiring the UI screenshot comprises:
taking a screenshot of a current UI page when an acceleration sensor monitors that a shaking value meets a predetermined condition, and
drawing characters and/or graphic marks on the screenshot of the current UI page to obtain the UI screenshot.

### Claim 7 (depends on 1)

The APP testing method of claim 1, wherein, when the APP records the key log related to user page display, a UI screenshot taken at that time is saved, and acquiring the UI screenshot comprises:
determining whether the key log is related to the user interface display; and
if the key log is related to the user interface display, acquiring, according to a moment recorded by the key log, the UI screenshot taken at the corresponding moment.

### Claim 8 (depends on 1)

The APP testing method of claim 1, wherein comparing the UI screenshot with the pre-stored UI design drawing comprises:
superimposing the UI design drawing on the UI screenshot; and
adjusting transparency of the UI design drawing, and displaying the difference between the UI screenshot and the UI design drawing.

### Claim 9 (depends on 1)

An electronic device, comprising:
one or more processors;
a memory having stored thereon one or more programs which, when executed by the one or more processors, cause the one or more processors to implement the APP testing method of claim 1; and
one or more I/O interfaces connected between the one or more processors and the memory, and configured to enable information interaction between the one or more processors and the memory.

### Claim 10 (depends on 1)

A computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the APP testing method of claim 1.
