Human-machine interaction interface traverse test method

Abstract

The invention discloses a human-machine interaction interface traverse test method, which is applied to a mobile terminal, and the human-machine interaction interface traverse test method comprises the following steps of a, setting a traverse test mode and traverse test strength, classifying the traverse mode according to a control type, and classifying the traverse strength according to an interface element route; b, embedding a control type and interface element route recognition module into the mobile terminal; c, opening one application, automatically scanning and recognizing control information and interface element routes of all interfaces of the application to generate a list, and selecting the traverse test mode and strength to carry out the traverse test; d, judging whether abnormality exits in the test process, and storing the abnormality information as a test text if abnormality exists; and e, judging whether the traverse test is completed or not, continuing the traverse test if the traverse test is not completed, and otherwise ending the test and saving a test result. Due to the adoption of the method, all interfaces in the application can be rapidly and accurately traversed, an abnormal position is automatically recorded, an abnormal log can be recorded, and users can conveniently take corresponding measures in time.

Description

technical field [0001] The invention relates to a testing method, in particular to a testing method for man-machine interaction interface traversal. Background technique [0002] The so-called traversal (Traversal) refers to doing one and only one visit to each node in the tree in turn along a certain search route. The operations performed by the access nodes depend on the specific application problem. Traversal is one of the most important operations on the binary tree, and it is the basis for other operations on the binary tree. Of course, the concept of traversal is also suitable for multi-element collections, such as arrays. [0003] At present, the tests aimed at the android application level are mainly a large number of out-of-order tests. Although this kind of test ensures the stability of the software itself, due to its out-of-order characteristics, we cannot accurately locate the specific components that cause errors. Our tests can't go deep into the root of the ...

AI Technical Summary

Problems solved by technology

[0003] At present, the tests aimed at the android application level are mainly a large number of out-of-order tests. Although this kind of test ensures the stability of the software itself, due to its out-of-order characteristics, we cannot accurately locate the specific components that cause errors. Our tests can't go deep into the root of the problem. According to the familiar description, this is a perceptual test. We stay on the surface of the application from beginning to end, and we can't make the test execute according to the steps we expected. The purpose of this kind of test is not strong, and we can only achieve the test effect we need by increasing the number of tests. If we cannot accurately obtain the conditions of all elements on the interface, we cannot quickly locate the checkpoint we need to test. This is what we The reason why it is often necessary to perform tens of thousands or even hundreds of thousands of operations when performing such tests

Images