Xcode project scheme is not currently configured for the test action

Question

I am trying to run an Xcode unit test for my iOS application. I am willing to do it on an iPad connected via USB to a Mac. I am trying to run the test from the command line in order to trigger it from Jenkins later on.

Below is what I'm currently typing into the command line and the error I'm getting. Please help.

The code:

xcodebuild test -scheme MyApplication -destination "platform=iOS,name=iPad"

The error:

Scheme MyApplication is not currently configured for the test action

It seems not a jenkins related issue since you are not using jenkins yet. I suggest you to remove the jenkins tag. And search for similar questions here to see whether they help or not. http://stackoverflow.com/questions/20237064/unable-to-execute-tests-from-command-line-via-xcodebuild http://stackoverflow.com/questions/25970396/xctool-fails-to-clean-my-ios-project — mainframer, May 27 '15 at 12:22
Thanks for the suggestion. I came across that example already. Looks like not directly related to my issue. In my case it is probably something to do with the schema sharing. I have a few schemes in my Xcode project, tried to share/unshare, delete and recreate them in different ways - still no luck.. — danR, May 27 '15 at 12:33

score 277 · Answer 1 · answered Mar 18 '16 at 18:49

277

For me the problem was that no tests were added to my scheme:

By adding test bundles to my scheme via the '+' button then the scheme could be built by Xcode and xcodebuild.

answered Mar 18 '16 at 18:49

David Hunt

3,300
2
18
11

7

It will also do this if you're trying to run them from the console while having the project open. – iwasrobbed Dec 06 '17 at 17:14
@iwasrobbed saved my day! this could be one of the answers rather than a comment – anoo_radha Jan 12 '18 at 15:19
1

I had the test scheme added, but "Test" was not checked. Checking that worked, – dsrees Apr 09 '18 at 14:17
How to open that menu ? – Bogdan Bogdanov Jul 08 '19 at 13:45
@BogdanBogdanov In the upper-left corner of Xcode just to the right of the 'Stop' button, click your Scheme and then click 'Edit Scheme...'. – David Hunt Jul 09 '19 at 14:09
My problem was that the folder of the project was in the folder of iCloud and my project didn't read the files as it have to. Thanks!!! – Bogdan Bogdanov Jul 09 '19 at 15:22
This was the root of the problem – Maria Jul 19 '22 at 08:43

score 46 · Answer 2 · edited Oct 26 '17 at 10:32

46

For everyone struggling with this problem.

My solution was to:

Select Test Target
Manage Scheme
Select Run in the left menu
Select Info in the tab
Choose Executable Target from the dropdown menu
Hit Close.

edited Oct 26 '17 at 10:32

Zonily Jame

5,053
3
30
56

answered Jan 31 '17 at 08:38

dan

873
8
11

This fixed it for us. I wonder if it has something to do with having Swift Package Manager libraries/frameworks included in your main app/target. Have not had to use this screen before (that I can recall) – race_carr Oct 20 '22 at 19:58

score 19 · Answer 3 · answered Jul 29 '20 at 11:08

Please follow following steps to resolve this error.

Select your project scheme at the top.
Click on Manage Schemes.
Select your test target in the popup.
Make sure to click on Edit button at the bottom left of popup.
Select Build.
Click the checkbox below "Run"
Close the popup.

score 18 · Answer 4 · answered May 27 '15 at 15:48

18

Fixed this up by removing duplicate schemes from Xcode. The schemes can be added/removed/shared/edited in Xcode via Product -> Scheme -> Manage Schemes.

answered May 27 '15 at 15:48

danR

1,518
2
11
15

2

Thanks! This was the clue I needed, and I'll mention a more subtle scenario that hit me: a second scheme, of the same name, but embedded in a dependent project. It seems this throws xcodebuild off, too, since it might favor the scheme inherited from a dependent project. – danielpunkass Jan 21 '16 at 13:57
2

To check for duplicate schemes run: `xcodebuild -workspace path/to/workspace/file -list` or `xcodebuild -project path/to/project/file -list`. Duplicate schemes can be leftovers from previous versions of the workspace, so a simple `git clean` may be all you need. – Ohad Schneider Dec 13 '16 at 18:36

score 3 · Answer 5 · answered May 10 '16 at 12:59

You should check your workspace data on Jenkins and see which *.xctest is already uploaded. Then you have to rename your UI/Unit test target to that *.xctest data in your xcode project like what you have on Jenkins and then push again.
OR wipe out your workspace from Jenkins and push all data again with new UI/Unit test target again.

(Of course you have to ensure that you have already made a scheme for project.)

score 1 · Answer 6 · answered Oct 10 '19 at 11:41

1

In my case I had no test file...

Here is a tutorial to perform UI Tests and create screenshots :

https://krausefx.com/blog/run-xcode-7-ui-tests-from-the-command-line

answered Oct 10 '19 at 11:41

Charly

436
4
12

score 1 · Answer 7 · answered Aug 10 '22 at 14:54

In my case, it was failing intermittently with this error, turns out I had two schemes with the same name and Xcode sometimes picked the wrong one, so make sure you do xcodebuild -workspace "MyWorkspace.xcworkspace" -list to see all your schemes and find out if you have repeating names.

score 0 · Answer 8 · answered Mar 05 '19 at 18:16

0

My problem was that the Tests.swift file was importing a module that no longer existed (I renamed the Targets for the project). Check to make sure all test files are importing currently existing modules.

answered Mar 05 '19 at 18:16

KVISH

12,923
17
86
162

score 0 · Answer 9 · answered Apr 24 '21 at 12:20

I was getting this similar error, but none of the other solutions helped. Since the error was first noticed while running via Fastlane, I next ran xcodebuild manually using this command to mimic the same.

xcodebuild -workspace Noname.xcworkspace -scheme Noname -enableCodeCoverage YES build-for-testing

I then saw errors regarding: Signing for "Noname-Dependency" requires a development team.

I also so reference to a macosx signing error, which I cannot sadly reproduce having since fixed the issue.

To fix the issue, under Signing & Capabilities for the Target I selected None and then under General I unchecked Mac, as we are not needing/using that but it was selected by default when creating this new project (CocoaPod).

Oddly enough, I added back Mac and things still kept working. I think that there is a oddity with the Xcode project file and/or scheme file(s) such that when you tinker enough with it -- things get reset/fixed.

score 0 · Answer 10 · answered Jun 23 '21 at 15:50

I had a test plan set up (xctestplan).

I needed a separate configuration for the tests (the test plan) in addition to "Shared Settings".
Please also make sure that the test plan (under Xcode scheme settings) includes a test target AND a configuration.

Screenshots attached:

score -1 · Answer 11 · answered Nov 08 '19 at 07:05

-1

Your test plan should have at least one custom configuration.

answered Nov 08 '19 at 07:05

Aleksey Tsyss

136
1
5

score -2 · Answer 12 · edited Feb 13 '21 at 07:30

-2

Go to Manage Schemes.
Delete all schemes and click on Autocreate Schemes.

edited Feb 13 '21 at 07:30

Jin Lee

3,194
12
46
86

answered Feb 12 '21 at 09:55

Ambesh Tiwari

648
7
11

Xcode project scheme is not currently configured for the test action

12 Answers12

My solution was to:

Linked