From dabeb1603cf146aa671dddf949788b514b983b76 Mon Sep 17 00:00:00 2001 From: Arturs Artamonovs Date: Tue, 28 Jul 2026 06:53:26 +0100 Subject: Initial Commit --- ShedCalcUITests/ShedCalcUITests.swift | 43 +++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) create mode 100644 ShedCalcUITests/ShedCalcUITests.swift (limited to 'ShedCalcUITests/ShedCalcUITests.swift') diff --git a/ShedCalcUITests/ShedCalcUITests.swift b/ShedCalcUITests/ShedCalcUITests.swift new file mode 100644 index 0000000..99d6f3c --- /dev/null +++ b/ShedCalcUITests/ShedCalcUITests.swift @@ -0,0 +1,43 @@ +// +// ShedCalcUITests.swift +// ShedCalcUITests +// +// Created by Jacky Jack on 28/07/2026. +// + +import XCTest + +final class ShedCalcUITests: XCTestCase { + + override func setUpWithError() throws { + // 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 + + // 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 tearDownWithError() throws { + // Put teardown code here. This method is called after the invocation of each test method in the class. + } + + @MainActor + func testExample() throws { + // UI tests must launch the application that they test. + let app = XCUIApplication() + app.launch() + + // Use XCTAssert and related functions to verify your tests produce the correct results. + // XCUIAutomation Documentation + // https://developer.apple.com/documentation/xcuiautomation + } + + @MainActor + func testLaunchPerformance() throws { + // This measures how long it takes to launch your application. + measure(metrics: [XCTApplicationLaunchMetric()]) { + XCUIApplication().launch() + } + } +} -- cgit v1.2.3