How to analyze 4399AT API operation events

This article mainly analyzes the relevant knowledge points of how to analyze 4399AT API operation events, the content is detailed and easy to understand, the operation details are reasonable, and has a certain reference value. If you are interested, you might as well follow the editor to have a look, and follow the editor to learn more about "how to analyze 4399AT API operation events".

API is mainly divided into three parts, including global configuration, use case configuration and operation events.

The following is mainly a textual description of the api of the action event:

Action:

Action type

Value:

Input for the text box, in conjunction with the action input

Hint:

String

The prompt of the input box

(for input type only) used to determine whether the input box has been emptied

InputType:

Only valid for input type. Currently, only username and password are supported.

Input:

Input operation, need to configure xpath,hint, value

UsrName indicates that the type entered is an account; password indicates that the type entered is a password

Click:

Click action, you need to configure xpath

Slide:

Slide (swipe up and down to find the control). You need to configure xpath loopTimes to represent the number of slides under this action.

SlideHori:

Slide left and right. You need to configure xpath loopTimes to indicate the number of slides under this action.

Check:

Check that you need to configure xpath to indicate whether the control exists. True is returned and false is not returned.

Back:

Return, indicating that the system return button is clicked

Tap:

Click on coordinates X.Y

Condition:

Condition, used in condition judgment

About "how to conduct 4399AT API operation event analysis" is introduced here, more related content can search previous articles, hope to help you answer questions, please support the website!