Repository navigation
test(e2e): extension RPC lifecycle and sandbox isolation - #1125
Merged
Merged
Conversation
…blewrap write isolation
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.
Part of #1053.
Starts a real driver process (a small python3 JSON-RPC stub, so the scenarios are skipped where python3 is missing) through
QueryaExtensionHarness:e2e_extension_rpc_lifecycle_test.dart: the whole lifecycle (handshake → connect → schema tree → query → disconnect → shutdown) passes; a driver that never answers the handshake fails fast and the remaining steps are skipped; a missing entry point is a launch failure.e2e_extension_sandbox_security_test.dart: a driver that tries to create a file on the host filesystem succeeds without a sandbox (control) and is blocked under bubblewrap. Skipped whenbwrapis not usable on the runner.The shared stub lives in
e2e_stub_driver.dart.