You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
40 lines
1.2 KiB
40 lines
1.2 KiB
// |
|
// watchUITests.m |
|
// watchUITests |
|
// |
|
// Created by xTT on 2017/7/3. |
|
// Copyright © 2017年 xTT. All rights reserved. |
|
// |
|
|
|
#import <XCTest/XCTest.h> |
|
|
|
@interface neutralWatchUITests : XCTestCase |
|
|
|
@end |
|
|
|
@implementation neutralWatchUITests |
|
|
|
- (void)setUp { |
|
[super setUp]; |
|
|
|
// Put setup code here. This method is called before the invocation of each test method in the class. |
|
|
|
// In UI tests it is usually best to stop immediately when a failure occurs. |
|
self.continueAfterFailure = NO; |
|
// UI tests must launch the application that they test. Doing this in setup will make sure it happens for each test method. |
|
[[[XCUIApplication alloc] init] launch]; |
|
|
|
// In UI tests it’s important to set the initial state - such as interface orientation - required for your tests before they run. The setUp method is a good place to do this. |
|
} |
|
|
|
- (void)tearDown { |
|
// Put teardown code here. This method is called after the invocation of each test method in the class. |
|
[super tearDown]; |
|
} |
|
|
|
- (void)testExample { |
|
// Use recording to get started writing UI tests. |
|
// Use XCTAssert and related functions to verify your tests produce the correct results. |
|
} |
|
|
|
@end
|
|
|