Enable running WordPressShared unit tests from Xcode and using Xcode MCP

[kean]

Problem

1. For some target like WordPressShared, Xcode has two shared schemes instead of one:

2. Neither of those schemes are configured for testing. The (WordPress project) one is, but it asks you to select a module it belongs to (it doesn't know). It won't let you pick WordPressShared either.

3. There are remnants on a test plan for WordPressShared, but they are broken

As a result, neither you not CC can run unit tests for individual targets using Xcode UI and/or Xcode MCP

Solution

1. Remove the duplicates schemes – keep only the "(Module)" one to match other targets
2. Add a working test plan to ./TestPlans/ (happy to discuss alternatives)
3. Configure the remaining scheme to use this test plan

Result

Future Changes

Update the rest of the schemes for the interval SwiftPM module in the same fashion to allow testing them directly from Xcode and using Xcode MCP.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[wpmobilebot]

📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.

	App Name	WordPress
	Configuration	Release-Alpha
	Build Number	31436
	Version	PR #25370
	Bundle ID	org.wordpress.alpha
	Commit	e6835fd
	Installation URL	4uh55gr38r5po

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[wpmobilebot]

📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.

	App Name	Jetpack
	Configuration	Release-Alpha
	Build Number	31436
	Version	PR #25370
	Bundle ID	com.jetpack.alpha
	Commit	e6835fd
	Installation URL	5sd0n0kftkrh0

Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

[wpmobilebot]

🤖 Build Failure Analysis

This build has failures. Claude has analyzed them - check the build annotations for details.

[jkmassel]

This seems like a good plan, but WDYT about putting the xctestplan in the WordPressSharedTests directory? That way each of these is colocated with their tests.

[kean]

This seems like a good plan, but WDYT about putting the xctestplan in the WordPressSharedTests directory? That way each of these is colocated with their tests.

I've considered this option. AI recommendation was the following:

I can't really think of strong pros and cons for either of the the options. For example, if the plans are not colocated, you can still pretty easily find all of the available plans using a filter:

It looks like we already have some module-specific plans colocated, so I'll update it and follow the current practice.

(Existing WordPressShared plan from the screenshot is broken btw)

[mokagio]

Looking good. I second @jkmassel 's comment regarding having the plan live in the same folder as the tests is manages.

I can see the value of a dedicated folder for plans if they were to combine different targets or different paths across targets, but since this is just an unfortunate requirement for testability with Xcode schemes, and the plan maps the whole tests target 1:1, it seems better for it to live in the same folder as the tests.

Anyways, looks like @kean already planned to address, so I'm preaching to the convert.

[kean]

Hmm, turns out, it's not as simple. The removal of ./WordPress/WordPress.xcodeproj/xcshareddata/xcschemes/WordPressShared.xcscheme was fine. There is always an auto-created scheme in ./Modules/.swiftpm/xcode/xcshareddata/xcschemes/WordPressReader.xcscheme. Unfortunately, the latter is in .gitignore.

The tests I configured briefly worked, but stopped after module reset.

The root cause is somewhere else. For some, reason the auto-created scheme for JetpackStats can find its respective tests.

The WordPressShared scheme can't.

I cleared cache and re-created the auto-created schemes and it was still the case.

It's a bit confusing that these schemes are marked as shared but are in .gitignore, so nothing gets shared.

[kean]

Since I recreated all the SwiftPM module schemes, JetpackStats tests also stopped working. Xcode now seems to put tests under Modules-Package by default.

I think what we might need to do is remove ./Modules/.swiftpm/xcode/xcshareddata/xcschemes from .gitignore and configure them properly for testing.

[mokagio]

I think what we might beed to do is remove ./Modules/.swiftpm/xcode/xcshareddata/xcschemes from .gitignore and configure them properly for testing.

That would have been my guess, too. However, what would happens once SwiftPM regenerates them?

[kean]

However, what would happens once SwiftPM regenerates them?

Presumably, it won't if it's shared. I'm going to give it a try. There must be a way to build and tests individual modules from Xcode for its MCP. It's a huge impediment when you are making module-specific changes.