From 7165263963d046fe8bd8a8abb542cb0bb34866b9 Mon Sep 17 00:00:00 2001 From: Vitaly Takmazov Date: Wed, 16 Sep 2020 17:39:47 +0300 Subject: NotificationService rewritten in Swift, added dummy test target # Conflicts: # Juick.xcodeproj/project.pbxproj # JuickPush/NotificationService.m --- JuickTests/JuickTests.swift | 43 +++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 43 insertions(+) create mode 100644 JuickTests/JuickTests.swift (limited to 'JuickTests') diff --git a/JuickTests/JuickTests.swift b/JuickTests/JuickTests.swift new file mode 100644 index 0000000..db40885 --- /dev/null +++ b/JuickTests/JuickTests.swift @@ -0,0 +1,43 @@ +// +// JuickTests.swift +// JuickTests +// +// Created by Vitaly Takmazov on 16.09.2020. +// Copyright © 2020 com.juick. All rights reserved. +// + +import XCTest + +class JuickTests: 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. + } + + func testExample() throws { + // UI tests must launch the application that they test. + let app = XCUIApplication() + app.launch() + + // Use recording to get started writing UI tests. + // Use XCTAssert and related functions to verify your tests produce the correct results. + } + + func testLaunchPerformance() throws { + if #available(macOS 10.15, iOS 13.0, tvOS 13.0, *) { + // This measures how long it takes to launch your application. + measure(metrics: [XCTApplicationLaunchMetric()]) { + XCUIApplication().launch() + } + } + } +} -- cgit v1.2.3