Skip to content

Conversation

mokagio
Copy link
Contributor

@mokagio mokagio commented May 12, 2025

Description

This PR adds a number of import statement that seem necessary to build Keystone for testing. Without them, on my machine, the build fails.

I landed on this PR via two different streams of work:

  • The idea of renaming WordPressUnitTests.xctestplan to KeystoneTests.xctestplan for clarity (not yet open as a PR)
  • The work to remove the workspace (Remove workspace file #24534) which required building and running tests for each framework target to identify issues in the migration

With both, I wanted to build Keystone for testing (Shift Cmd U), and got compilation failures. Many iterations later, all the required imports are in place.

The reason we never noticed despite having a CI step to run Keystone tests is that the scheme was not (never was? 🤔 ) configured to run tests

image

This has now been rectified.

Testing instructions

@dangermattic
Copy link
Collaborator

dangermattic commented May 12, 2025

1 Message
📖 This PR is still a Draft: some checks will be skipped.

Generated by 🚫 Danger

@wpmobilebot
Copy link
Contributor

wpmobilebot commented May 12, 2025

App Icon📲 You can test the changes from this Pull Request in Jetpack by scanning the QR code below to install the corresponding build.
App NameJetpack
ConfigurationRelease-Alpha
Build Number28006
VersionPR #24537
Bundle IDcom.jetpack.alpha
Commite76609c
Installation URL1c4kd1c0obkvg
Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

@wpmobilebot
Copy link
Contributor

wpmobilebot commented May 12, 2025

App Icon📲 You can test the changes from this Pull Request in WordPress by scanning the QR code below to install the corresponding build.
App NameWordPress
ConfigurationRelease-Alpha
Build Number28006
VersionPR #24537
Bundle IDorg.wordpress.alpha
Commite76609c
Installation URL5hr3c9isg71rg
Automatticians: You can use our internal self-serve MC tool to give yourself access to those builds if needed.

@mokagio mokagio added this to the 26.1 milestone May 13, 2025
@mokagio mokagio self-assigned this May 13, 2025
@mokagio mokagio added the Tooling Build, Release, and Validation Tools label May 13, 2025
@mokagio mokagio force-pushed the mokagio/add-imports-keystone branch 5 times, most recently from 5cc5a08 to 02f660f Compare May 20, 2025 06:55
@mokagio mokagio force-pushed the mokagio/add-imports-keystone branch 4 times, most recently from e1eb12f to a991701 Compare May 23, 2025 01:41
@mokagio mokagio force-pushed the mokagio/add-imports-keystone branch 5 times, most recently from 92de5e1 to 56c4ada Compare June 25, 2025 04:12
@mokagio mokagio force-pushed the mokagio/add-imports-keystone branch from b21014f to 47ea74f Compare June 26, 2025 05:43
@mokagio mokagio changed the title Add imports required to compile Keystone for testing Allow running WordPressTests standalone via the Keystone scheme Jun 26, 2025
@mokagio mokagio force-pushed the mokagio/add-imports-keystone branch from 47ea74f to e76609c Compare June 26, 2025 09:46
Copy link

@wpmobilebot wpmobilebot modified the milestones: 26.1, 26.2 Aug 8, 2025
@wpmobilebot
Copy link
Contributor

Version 26.1 has now entered code-freeze, so the milestone of this PR has been updated to 26.2.

@kean kean modified the milestones: 26.2, Someday Aug 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Tooling Build, Release, and Validation Tools
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants