blob: a7f33c3c2c9894c7b7c6393628c4372db69b7279 [file] [log] [blame]
Guillaume Roguezd0a1faf2016-06-29 15:55:37 -04001//
2// RingUITests.swift
3// RingUITests
4//
5// Created by Edric on 16-06-23.
6// Copyright © 2016 Savoir-faire Linux. All rights reserved.
7//
8
9import XCTest
10
11class RingUITests: XCTestCase {
Thibault Wittemberg14b092a2017-07-04 18:13:26 -040012
Guillaume Roguezd0a1faf2016-06-29 15:55:37 -040013 override func setUp() {
14 super.setUp()
Thibault Wittemberg14b092a2017-07-04 18:13:26 -040015
Guillaume Roguezd0a1faf2016-06-29 15:55:37 -040016 // Put setup code here. This method is called before the invocation of each test method in the class.
Thibault Wittemberg14b092a2017-07-04 18:13:26 -040017
Guillaume Roguezd0a1faf2016-06-29 15:55:37 -040018 // In UI tests it is usually best to stop immediately when a failure occurs.
19 continueAfterFailure = false
20 // UI tests must launch the application that they test. Doing this in setup will make sure it happens for each test method.
21 XCUIApplication().launch()
22
23 // 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.
24 }
Thibault Wittemberg14b092a2017-07-04 18:13:26 -040025
Guillaume Roguezd0a1faf2016-06-29 15:55:37 -040026 override func tearDown() {
27 // Put teardown code here. This method is called after the invocation of each test method in the class.
28 super.tearDown()
29 }
Thibault Wittemberg14b092a2017-07-04 18:13:26 -040030
Guillaume Roguezd0a1faf2016-06-29 15:55:37 -040031 func testExample() {
32 // Use recording to get started writing UI tests.
33 // Use XCTAssert and related functions to verify your tests produce the correct results.
34 }
Thibault Wittemberg14b092a2017-07-04 18:13:26 -040035
Guillaume Roguezd0a1faf2016-06-29 15:55:37 -040036}