[react-devtools-cdt-mcp] add chrome-devtools E2E coverage#36823
Open
hoxyq wants to merge 1 commit into
Open
Conversation
hoxyq
force-pushed
the
rtcm-1-cdt-mcp-e2e
branch
from
a65e637 to
f6d1472
Compare
hoxyq
force-pushed
the
rtcm-1-cdt-mcp-e2e
branch
from
f6d1472 to
192c850
Compare
daltino
reviewed
Jun 19, 2026
daltino
left a comment
daltino
left a comment
There was a problem hiding this comment.
DECISION: APPROVE
This PR introduces E2E test coverage for the chrome-devtools integration within react-devtools-cdt-mcp. It adds a robust testing script (run.flow.js), updates the package configuration to support E2E tests, and includes relevant dependency updates. The changes align with the contribution guidelines and improve test automation, making it a valuable addition.
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
2 participants
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.
A node runner that bootstraps
fixtures/app, and then useschrome-devtoolsCLI to test third-party tools.