Using the XCTest (or XCUITest) test framework? Follow the instructions below to report results. If you are not using XCTest please see the Swift docs for integrating with a lower-level library.

An alternative way to report results if you do not want to follow the instructions below is to utilize the JUnit XML output from XCTest but the method below is recommended because you can also upload files that way.

Add the tesults-xctest-observer package as a dependency to your project. Search for tesults-xctest-observer in Xcode to find the package.

Ensure you install version 1.0.4 or higher. You can verify the version you have installed by checking package dependencies.

If you see a build error related to XCTest not being found, ensure the 'Enable Testing Search Paths' option is set to Yes for your app target.

You are required to register the tesults-xctests-observer at the startup of your tests as described in the overview section for XCTestsObservationCenter. Specifically this requires creating a new Swift class that at a minimum does the following:

//
//  Start.swift
//  iphone-app
//
//

import Foundation
import XCTest
@testable import tesults_xctest_observer

class Start : NSObject {
  override init () {
    super.init()
    XCTestObservationCenter.shared.addTestObserver(TesultsXCTestObserver(target: "token"))
  }
}

The 'token' value above should be replaced with your Tesults target token. If you have lost your token you can regenerate one from the config menu.

Now set the NSPrincipalClass key in your Info.plist to the class you created to register the observer:

If Tesults upload does not take place check your terminal output in Xcode to see whether there is an error message related to not being able to find the NSPrincipalClass you specified. This error must be resolved. A couple of things to check. First ensure your NSPrincipalClass is in the Compile Sources list of Build Phases for your target:

If the above is correct, then you likey have an issue with the name itself. This needs to be the name of your target followed by a dot and the name of the class you are using as your NSPrincipalClass.

Files generated by tests

Attach files during a test using the tesults-xctests-observer file function (example below). Files attached this way will be automatically uploaded to Tesults for reporting.

import tesults_xctest_observer
...

// Run this code inside a test function otherwise replace the
// 'self' reference with a reference to the running test
TesultsXCTestObserver.file(testCase: self, path: "full/path/to/file/screenshot.png")
TesultsXCTestObserver.file(testCase: self, path: "full/path/to/file/log.txt")

Caution: If uploading files the time taken to upload is entirely dependent on your network speed. Typical office upload speeds of 100 - 1000 Mbps should allow upload of even hundreds of files quite quickly, just a few seconds, but if you have slower access it may take hours. We recommend uploading a reasonable number of files for each test case. The upload method blocks at the end of a test run while uploading test results and files. When starting out test without files first to ensure everything is setup correctly.

TesultsXCTestObserver parameters

Target

targetRequired

Required arg to upload to Tesults, if this arg is not provided the reporter does not attempt upload, effectively disabling it. Get your target token from the configuration menu in the Tesults web interface.

TesultsXCTestObserver(target: "token")

buildNameOptional

Use this to report a build version or name for reporting purposes.

buildResultOptional

Use this to report the build result, must be one of [pass, fail, unknown].

buildDescriptionOptional

Use this to report a build description for reporting purposes.

buildReasonOptional

Use this to report a build failure reason.

XCTestObservationCenter.shared.addTestObserver(
  TesultsXCTestObserver(
    target: "token",
    buildName: "1.0.0",
    buildDescription: "build description here",
    buildResult: "fail",
    buildReason: "Failure reason here"
  )
)

Result interpretation is not currently supported by this integration. If you are interested in support please contact help@tesults.com.