Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
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.
What changed
Harness now has a first-class plugin system. Users can register Harness plugins in
rn-harness.config.*, and those plugins can tap into key lifecycle and runtime events during a test run.Why this was added
Plugins give us a stable extension point for features that should live outside core Harness. Instead of adding plugin-specific config fields or platform APIs directly to Harness, we can build those features as plugins.
What Harness plugins are
Harness plugins are user-configured extensions loaded from the Harness config file. A plugin can observe or react to events such as Harness startup, Metro activity, app lifecycle signals, collection, and test execution, and run custom Node.js logic around them.
What this enables
This is the foundation for custom integrations such as native coverage collection, reporting, or other workflow-specific extensions, while keeping the core Harness API smaller and cleaner.
Also included
@react-native-harness/pluginspackage built onhookable