docs(testing): clarify extension integration homes - #134
Merged
Conversation
Route UI/state and composed-background coverage through existing Extension test locations so agents avoid unnecessary E2E tests or new layers. Co-authored-by: Cursor <cursoragent@cursor.com>
racitores
marked this pull request as ready for review
August 24, 2026 17:03
racitores
enabled auto-merge (squash)
August 25, 2026 08:00
jvbriones
approved these changes
Aug 25, 2026
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.
Description
Clarify the existing MetaMask Extension integration boundaries without introducing a new testing layer or runner.
test/integration/.MetaMaskControllerand child-controller wiring to the existing Node tests underapp/scripts/.Type of Change
Checklist
Testing
yarn audit:skills(0 errors; pre-existing warnings only)yarn test(65 tests passed)git diff --checkAdditional Context
This deliberately does not add a Mobile-style component-view or controller integration harness. It documents two existing homes within Extension's current three-layer model and prevents controller-composition coverage from defaulting to E2E.
Made with Cursor