iOS9 UI Tests Exploration Notes

What are UI Tests?

UI Tests is a Testing component that automatically tests UI and interactions

What are UI Tests good for?

It can realize functions such as automatically clicking a button, view, or automatically entering text by writing code or recording the developer's operation process and coding it.

Importance of UI Tests

In the actual development process, as the project grows bigger and more and more functions are added, it is very difficult to cover all test cases by manual operation alone. Especially after adding new functions, the old functions must be retested, which results in a lot of time spent on regression testing. A lot of repetitive work is generated here, and some of this repetitive work can be done automatically. At this time, UI Tests can help solve this problem.

How to use

Step 1: Add UI Tests

If it is a new project, you can directly check the option when creating the project, as shown below

If it is an existing project, you can add a UI Tests by adding a target. Click the Xcode menu and find the target column.

In the Test options, select Cocoa Touch UI Testing Bundle

At this time, the test component is added successfully, and its location in the project is shown in the figure below

Step 2: Create test code

Manually create test code

Open the test file and add the test code to the testExample() method

If you don't know how to write test code, you can refer to the automatically generated code style

Automatically generate test steps

After selecting the test file, click the Record button

Start the operation at this time, it will record your operation steps and generate test code

The following figure shows the test code automatically generated after some operations

At this time, you can analyze the syntax of the test code so that you can manually modify or write the test code yourself

Start Testing

Click the play button next to the testExample method and it will start the automatic test. You will see the app automatically operating.

The following is the syntax of the test element:

XCUIApplication:

Inheriting XCUIElement, this class manages the life cycle of the application and contains two main methods

launch():

Start the program

terminate():

Termination Program

XCUIElement:

Inherit NSObject and implement protocols XCUIElementAttributes, XCUIElementTypeQueryProvider

Can represent various UI elements of the system

exist:

It allows you to determine whether the current UI element exists. If you operate on a non-existent element, the test component will throw an exception and interrupt the test.

descendantsMatchingType(type:XCUIElementType)->XCUIElementQuery:

Get a certain type of element and its subclass collection

childrenMatchingType(type:XCUIElementType)->XCUIElementQuery:

Get a set of elements of a certain type, excluding its subclasses

The difference between these two methods is that when you only use the system UIButton, you can use childrenMatchingType. If you also want to query the child Buttons you defined, you must use descendantsMatchingType.

In addition, UI elements have some interactive methods

tap(): click

doubleTap(): double tap

pressForDuration(duration: NSTimeInterval): Press for a while. This is useful when you need to perform a delayed operation.

swipeUp(): This does not respond to the pan gesture. I haven't found where it can be used yet. It may also be a bug in the beta version. I won't explain it yet.

typeText(text: String): used for text input in textField and textView. Before using, make sure the text box has input focus. You can use the tap() function to make it have focus.

XCUIElementAttributes Protocol

It contains some properties in UIAccessibility

As shown below

It is convenient for you to view the characteristics of the current element. The identifier attribute can be used to directly read the element. However, this attribute has a bug in UITextField. The reason is not clear yet.

XCUIElementTypeQueryProvider Protocol

It contains most of the UI control types in the system, and you can get a certain type of UI collection by reading properties.

Some of the properties are shown below:

Create a Demo

First create a login page

Click the login button to log in and click the clear button to clear the text.

After successful login, you can go to the personal information page

The personal information page is as follows

Click the modify button to modify personal information, and click the Message button to view personal messages.

*** is the message interface

Testing the login page

Enter an incorrect account number

Verify the results

Close the warning window

Clear input records

Enter a valid account number

Verify the results

Go to the personal information page

The test code is as follows:

 func testLoginView() {
 let app = XCUIApplication()
 // Since there is a problem with the UITextField id, you can only read it by traversing the elements through the label method  
 let nameField = self.getFieldWithLbl( "nameField" )
 if self.canOperateElement(nameField) {
 nameField!.tap()
 nameField!.typeText( "xiaoming" )
 }
 let psdField = self.getFieldWithLbl( "psdField" )
 if self.canOperateElement(psdField) {
 psdField!.tap()
 psdField!.typeText( "1234321" )
 }
 // Read the corresponding button through the preset id of UIButton  
 let loginBtn = app.buttons[ "Login" ]
 if self.canOperateElement(loginBtn) {
 loginBtn.tap()
 }
 // Start a delay. Since the real login is an Internet request, the result cannot be obtained directly. The demo simulates the Internet request by delaying.  
 let window = app.windows.elementAtIndex( 0 )
 if self.canOperateElement(window) {
 // Delay for 3 seconds. If the login is successful after 3 seconds, the user will automatically enter the information page. If the login fails, a warning window will pop up.  
 window.pressForDuration( 3 )
 }
 // The alert id and labe cannot be used, it is probably a bug, so we can only judge by the number  
 if app.alerts.count > 0 {
 // Login failed  
 app.alerts.collectionViews.buttons[ "OK" ].tap()
 let clear = app.buttons[ "Clear" ]
 if self.canOperateElement(clear) {
 clear.tap()
 if self.canOperateElement(nameField) {
 nameField!.tap()
 nameField!.typeText( "sun" )
 }
 if self.canOperateElement(psdField) {
 psdField!.tap()
 psdField!.typeText( "111111" )
 }
 if self.canOperateElement(loginBtn) {
 loginBtn.tap()
 }
 if self.canOperateElement(window) {
 // Delay for 3 seconds. If the login is successful after 3 seconds, the user will automatically enter the information page. If the login fails, a warning window will pop up.  
 window.pressForDuration( 3 )
 }
 self.loginSuccess()
 }
 } else {
 // Login successful  
 self.loginSuccess()
 }
 }

There are a few points that require special attention:

1. When your element does not exist, it may still return an element object, but you cannot operate on it at this time

2. When the element you want to tap is blocked by the keyboard or UIAlertView, executing the tap method will throw an exception

For detailed implementation, please refer to demo: https://github.com/sunGd/demo/tree/master/iOS9/UITestDemo

Personal information page test

Change gender

Modify age

Modify mood

Save changes

The test code is as follows:

 func testInfo() {
 let app = XCUIApplication()
 let window = app.windows.elementAtIndex( 0 )
 if self.canOperateElement(window) {
 // Delay 2 seconds, loading data takes time  
 window.pressForDuration( 2 )
 }
 let modifyBtn = app.buttons[ "modify" ];
 modifyBtn.tap()
 let sexSwitch = app.switches[ "sex" ]
 sexSwitch.tap()
 let incrementButton = app.buttons[ "Increment" ]
 incrementButton.tap()
 incrementButton.tap()
 incrementButton.tap()
 app.buttons[ "Decrement" ].tap()
 let textView = app.textViews[ "feeling" ]
 textView.tap()
 app.keys[ "Delete" ].tap()
 app.keys[ "Delete" ].tap()
 textView.typeText( " abc " )
 // Click on the blank area  
 let clearBtn = app.buttons[ "clearBtn" ]
 clearBtn.tap()
 // Save data  
 modifyBtn.tap()
 window.pressForDuration( 2 )
 let messageBtn = app.buttons[ "message" ]
 messageBtn.tap();
 // Delay 1 second, pushing view takes time  
 window.pressForDuration( 1 )
 self.testMessage()
 }

There are two points that require special attention:

1. The focus position cannot be selected when the textview gets the focus

2. The trigger position of the tap event is the center of the view, so when the center of the view is blocked, consider using other views instead.

Personal message interface test

Click on the cell

The test code is as follows:

 func testMessage() {
 let app = XCUIApplication()
 let window = app.windows.elementAtIndex( 0 )
 if self.canOperateElement(window) {
 // Delay 2 seconds, loading data takes time  
 window.pressForDuration( 2 )
 }
 let table = app.tables
 table.childrenMatchingType(.Cell).elementAtIndex( 8 ).tap()
 table.childrenMatchingType(.Cell).elementAtIndex( 1 ).tap()
 }

One thing to note here:

1. Unable to obtain the element pointer of tableView temporarily

Summarize

In general, UI Tests can only be used to test some basic functions, verify whether the app functions can be used normally, and whether there are crashes. But it also has many shortcomings. The process of writing test cases is very cumbersome, the automatically generated code is almost impossible to run, the function is single, many test cases cannot be covered, and there are many bugs, which greatly limits the application of UI Tests in actual development. I hope that these problems can be fixed and more functions can be opened when the official version comes out.