A method, device, and device for testing push messages

Abstract

The present invention discloses a method for testing a push message, wherein the method includes: detecting whether a terminal has received the push message; if it is detected that the terminal has received the push message, parsing the push message to obtain attribute information of the push message The attribute information of the push message at least includes the identification information, message title and message content of the application under test corresponding to the push message; packaging the identification information, message title and message content of the application under test according to a preset format , get a heartbeat message; send the heartbeat message to the server; judge whether the heartbeat message is sent successfully; if the heartbeat message is not sent successfully, store the heartbeat message locally. The invention also discloses a device and equipment for testing push messages.

Description

technical field [0001] The present invention relates to terminal testing technology, in particular to a method, device and equipment for testing push messages. Background technique [0002] As the most important operation method for mobile application (APP, Application, application for short) product operation, message push (Message Push) is valued by more and more application manufacturers. Message push has the following important impacts on application operations. 1) It can increase product activity. The number of active users is the foundation of application survival, and only users can bring value to the product; message push is to get special attention from users, and open the application to activate it. an excellent way. 2) Increase user stickiness; "viscosity" is an important indicator to measure user loyalty, and message push can improve user utilization rate and user loyalty; 3) In the process of user operation, wake up sleeping users and retain lost users. Improv...

AI Technical Summary

Problems solved by technology

The disadvantages of the prior art are: 1) Testers need to retrieve logs from each test device. Generally speaking, the number of test devices is relatively small, and only a certain number of test devices can represent the general situation, that is, one test device cannot represent The overall situation; in addition, because the prior art is manual acquisition of logs, it is impossible to set too many test equipment; 2) There is a certain gap between the test environment and the actual operating environment, and the methods of the prior art can only be used It cannot be used in the actual operating environment; 3) After the updated version is applied, the developer needs to recompile the log package with the push message; 4) Whether it is the software upgrade in the background server or the protocol data change in the log, the comparison algorithm needs to be re-adapted 5) If the test equipment is offline, the root cause cannot be determined if the message is missed

Images