From 152b21222bb6759de69c1abfb5b5b73496aa1460 Mon Sep 17 00:00:00 2001 From: Dylan Bolger Date: Mon, 3 Sep 2018 16:06:39 -0500 Subject: Initial Commit --- DWA140MenuUITests/DWA140MenuUITests.swift | 36 +++++++++++++++++++++++++++++++ 1 file changed, 36 insertions(+) create mode 100644 DWA140MenuUITests/DWA140MenuUITests.swift (limited to 'DWA140MenuUITests/DWA140MenuUITests.swift') diff --git a/DWA140MenuUITests/DWA140MenuUITests.swift b/DWA140MenuUITests/DWA140MenuUITests.swift new file mode 100644 index 0000000..1110ead --- /dev/null +++ b/DWA140MenuUITests/DWA140MenuUITests.swift @@ -0,0 +1,36 @@ +// +// DWA140MenuUITests.swift +// DWA140MenuUITests +// +// Created by Dylan Bolger on 9/3/18. +// Copyright © 2018 Dylan Bolger. All rights reserved. +// + +import XCTest + +class DWA140MenuUITests: XCTestCase { + + override func 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. + continueAfterFailure = false + // UI tests must launch the application that they test. Doing this in setup will make sure it happens for each test method. + XCUIApplication().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. + } + + override func tearDown() { + // Put teardown code here. This method is called after the invocation of each test method in the class. + super.tearDown() + } + + func testExample() { + // Use recording to get started writing UI tests. + // Use XCTAssert and related functions to verify your tests produce the correct results. + } + +} -- cgit v1.2.3