-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Allow running WordPressTests standalone via the Keystone scheme #24537
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
mokagio
wants to merge
14
commits into
trunk
Choose a base branch
from
mokagio/add-imports-keystone
base: trunk
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Generated by 🚫 Danger |
|
App Name | Jetpack | |
Configuration | Release-Alpha | |
Build Number | 28006 | |
Version | PR #24537 | |
Bundle ID | com.jetpack.alpha | |
Commit | e76609c | |
Installation URL | 1c4kd1c0obkvg |
|
App Name | WordPress | |
Configuration | Release-Alpha | |
Build Number | 28006 | |
Version | PR #24537 | |
Bundle ID | org.wordpress.alpha | |
Commit | e76609c | |
Installation URL | 5hr3c9isg71rg |
5cc5a08
to
02f660f
Compare
e1eb12f
to
a991701
Compare
92de5e1
to
56c4ada
Compare
This was referenced Jun 26, 2025
The only iOS version available out of the box with the 16.3 stack.
b21014f
to
47ea74f
Compare
import
s required to compile Keystone for testingJust trying to understand why Keystone fails to build for testing. Using forward declarations keeps the headers and the compilation leaner.
Clearly the issues documented in some of the usages were temporary due to the transition.
47ea74f
to
e76609c
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
WordPressUnitTests.xctestplan
toKeystoneTests.xctestplan
for clarity (not yet open as a PR)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
This has now been rectified.
Testing instructions