> ## Content Index
> Fetch the complete content index at: https://williamboles.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Runnable Test Schemes for Travis CI
- URL: https://williamboles.com/running-your-unit-tests/
- Published: 2016-02-27T14:23:20.000Z
- Updated: 2026-09-26T16:34:32.000Z
- Description: No one said running your unit tests on Travis CI would be easy. Who knew running tests via the Xcode UI wasn't the same as running those tests via the terminal 🤷‍♂️? Here, we look at how to prepare your test targets for running on Travis CI.
- Author: William Boles
- Tags: CI, Xcode, Testing

When I first created [ConvenientFileManager](https://github.com/wibosco/ConvenientFileManager?ref=williamboles.com), I didn't add a unit testing target - what can I say, I was young(er) and foolish. Recently I decided to rectify this grievous error and added a unit testing target. After writing the tests, I pushed them to my repo, and CI took over. However, [Travis CI](https://travis-ci.org/wibosco/ConvenientFileManager?ref=williamboles.com) ran into some trouble when attempting to run this test target, resulting in the following error:

```
The command "xctool -project ConvenientFileManager.xcodeproj -scheme ConvenientFileManager build -scheme ConvenientFileManagerTests test -sdk iphonesimulator" exited with 1.
```

Debugging on Travis CI isn't a time-efficient task, so I needed to reproduce the error on my local machine. However, when I ran the tests via Xcode, everything was fine 🤔. Keen to avoid a "it's fine on my computer" moment, I decided to look again at how the tests were executed on Travis. I quickly discovered that my attempt to reproduce the error was fundamentally flawed - I was running the tests via the Xcode UI whereas on Travis I was using `xctool`. Switching over to the terminal I ran the same command as happens on Travis:

```
xctool -project ConvenientFileManager.xcodeproj -scheme ConvenientFileManager build -scheme ConvenientFileManagerTests test -sdk iphonesimulator
```

With the above command, I was able to reproduce the error on my local machine and could begin the process of debugging it. After *much* investigation I stumbled upon the solution - I had to manually mark the `ConvenientFileManagerTests` scheme as **runnable**:

![Test scheme marked as runnable](https://storage.ghost.io/c/b9/b4/b9b42214-5933-4584-8e56-9ee8ca21d23b/content/images/size/w1000/2016/02/Runnable-Tests.png)

With that tick on `Run`, my tests started running on Travis 😁 - all that hassle because when creating the project, I didn't think I needed unit tests, so I didn't tick the "Include Unit Tests" tickbox 😢. Lesson learnt.