From 2feb019c373c99fa3840d99724f5ee6f7c4dac36 Mon Sep 17 00:00:00 2001 From: Abdellah El Morabit Date: Mon, 18 Nov 2024 19:23:17 +0100 Subject: started switching to c, started the web gui, started the gtk gui, ending the swift version --- I2C/I2CUITests/I2CUITests.swift | 42 ----------------------------------------- 1 file changed, 42 deletions(-) delete mode 100644 I2C/I2CUITests/I2CUITests.swift (limited to 'I2C/I2CUITests/I2CUITests.swift') diff --git a/I2C/I2CUITests/I2CUITests.swift b/I2C/I2CUITests/I2CUITests.swift deleted file mode 100644 index a98bb08..0000000 --- a/I2C/I2CUITests/I2CUITests.swift +++ /dev/null @@ -1,42 +0,0 @@ -// -// I2CUITests.swift -// I2CUITests -// -// Created by nsrddyn on 09/11/2024. - -import XCTest - -final class I2CUITests: 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. - } - - @MainActor - func testLaunchPerformance() throws { - if #available(macOS 10.15, iOS 13.0, tvOS 13.0, watchOS 7.0, *) { - // This measures how long it takes to launch your application. - measure(metrics: [XCTApplicationLaunchMetric()]) { - XCUIApplication().launch() - } - } - } -} -- cgit v1.2.3-70-g09d2