You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 3, 2024. It is now read-only.
Moved these tests out of test/standalone (with path changes and minor fixes to make them run independently of each other):
test-debuglet.js
test-module.js
test-options-credentials.js
test-sourcemapper.js
Also, moved test-v8debugapi.js back to test/standalone. Because it's always run last it didn't seem to have interference with other tests. But now that test-module.js is non-interference, test-v8debugapi.js fails unless being run alone.
All of the remaining standalone tests have to do with the v8debugapi object, which is a singleton. To make these tests standalone would involve adding a debug-only function to src/v8debugapi.js to modify the singleton... but was not sure if this would be a reasonable thing to do. Opinions wanted here.
I'd be okay with adding a test-only API into src/v8debugapi.js to make the tests stateless. We don't export this file outside the module, so I don't have concerns about the misuse of the test-only API.
@ofrobots As it turns out, having tests being non-interfering also requires a change in index.js itself, to override the debuglet singleton (see here). Do you think I should go ahead with this, and if so, what would be a more suitable approach: exposing a test-only stop method, or enabling a test-only force flag that causes debuglet to be re-assigned when set? (I am leaning towards the latter.)
I like the idea of a test-only stopAgent method better, but I don't have really strong feelings on this.
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
cla: yesThis human has signed the Contributor License Agreement.
3 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.
Moved these tests out of
test/standalone(with path changes and minor fixes to make them run independently of each other):test-debuglet.jstest-module.jstest-options-credentials.jstest-sourcemapper.jsAlso, moved
test-v8debugapi.jsback totest/standalone. Because it's always run last it didn't seem to have interference with other tests. But now thattest-module.jsis non-interference,test-v8debugapi.jsfails unless being run alone.All of the remaining standalone tests have to do with the
v8debugapiobject, which is a singleton. To make these tests standalone would involve adding a debug-only function tosrc/v8debugapi.jsto modify the singleton... but was not sure if this would be a reasonable thing to do. Opinions wanted here.