Build and test Keystone and WordPressData in CI

[mokagio]

While neither framework is good to go, I find it useful to have CI feedback on their compilation and unit tests status.

Granted, Keystone has no tests at the moment, but at least we have the step in place.

As for WordPressData, there are only two dummy tests, but, again, at least it's in place. #24378 and its follow ups will changes this.

[dangermattic]

	1 Warning
⚠️	This PR is assigned to the milestone 25.9. The due date for this milestone has already passed. Please assign it to a milestone with a later deadline or check whether the release for this milestone has already been finished.

Generated by 🚫 Danger

[Copilot]

Pull Request Overview

This PR introduces new CI steps for running unit tests on the Keystone and WordPressData frameworks, providing immediate feedback on compilation and test results.

• Adds a CI step for Keystone unit tests
• Adds a CI step for WordPressData unit tests

Files not reviewed (1)

• WordPress/WordPress.xcodeproj/xcshareddata/xcschemes/Keystone.xcscheme: Language not supported

Comments suppressed due to low confidence (2)

.buildkite/pipeline.yml:87

• [nitpick] Consider renaming the context to 'Keystone Unit Tests' to maintain consistency with the step label.

context: "Unit Tests Keystone"

.buildkite/pipeline.yml:101

• [nitpick] Consider renaming the context to 'WordPressData Unit Tests' to align with the step label and improve consistency.

context: "Unit Tests WordPressData"

[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	27043
	Version	PR #24391
	Bundle ID	org.wordpress.alpha
	Commit	0ae6031
	Installation URL	2grqniquvcqm8

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	27043
	Version	PR #24391
	Bundle ID	com.jetpack.alpha
	Commit	0ae6031
	Installation URL	5i16io6fvcck8

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

[crazytonyli]

Switching to fastlane to be consistent with how other tests execute?

[mokagio]

Good observation. To do this, we'd need a custom lane. Alternatively, we could do bundle exec fastlane run scan... but at that point, that's not that different from calling xcodebuild.

I didn't document that, but I see these steps as temporary only, just to get fast CI feedback for these foundational modules that are still in flux. That is, we should get to the point when they are properly integrated and they run as part of the apps test suites, or to the point where the apps are but thin shelters and then we'd think about how to test all modules and frameworks in isolation and fast in CI.