| 1 |
efrain |
1 |
//
|
|
|
2 |
// twogetskillsUITests.swift
|
|
|
3 |
// twogetskillsUITests
|
|
|
4 |
//
|
|
|
5 |
// Created by Efrain Yanez Recanatini on 1/12/22.
|
|
|
6 |
//
|
|
|
7 |
|
|
|
8 |
import XCTest
|
|
|
9 |
|
|
|
10 |
class twogetskillsUITests: XCTestCase {
|
|
|
11 |
|
|
|
12 |
override func setUpWithError() throws {
|
|
|
13 |
// Put setup code here. This method is called before the invocation of each test method in the class.
|
|
|
14 |
|
|
|
15 |
// In UI tests it is usually best to stop immediately when a failure occurs.
|
|
|
16 |
continueAfterFailure = false
|
|
|
17 |
|
|
|
18 |
// 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.
|
|
|
19 |
}
|
|
|
20 |
|
|
|
21 |
override func tearDownWithError() throws {
|
|
|
22 |
// Put teardown code here. This method is called after the invocation of each test method in the class.
|
|
|
23 |
}
|
|
|
24 |
|
|
|
25 |
func testExample() throws {
|
|
|
26 |
// UI tests must launch the application that they test.
|
|
|
27 |
let app = XCUIApplication()
|
|
|
28 |
app.launch()
|
|
|
29 |
|
|
|
30 |
// Use recording to get started writing UI tests.
|
|
|
31 |
// Use XCTAssert and related functions to verify your tests produce the correct results.
|
|
|
32 |
}
|
|
|
33 |
|
|
|
34 |
func testLaunchPerformance() throws {
|
|
|
35 |
if #available(macOS 10.15, iOS 13.0, tvOS 13.0, *) {
|
|
|
36 |
// This measures how long it takes to launch your application.
|
|
|
37 |
measure(metrics: [XCTApplicationLaunchMetric()]) {
|
|
|
38 |
XCUIApplication().launch()
|
|
|
39 |
}
|
|
|
40 |
}
|
|
|
41 |
}
|
|
|
42 |
}
|