test: Reenable the drag-out-every-test-block browser tests - #10396
Open
gonfunko wants to merge 1 commit into
Open
test: Reenable the drag-out-every-test-block browser tests#10396gonfunko wants to merge 1 commit into
gonfunko wants to merge 1 commit into
Conversation
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.
The basics
The details
Resolves
Fixes #10213
Proposed Changes
This PR reenables the two browser tests that exercise dragging out every block from the block-test plugin into the workspace. This change was LLM-assisted; the path for the block-test plugin is dynamically resolved from the monorepo, and the source gets executed inside the WebDriver browser session to define the blocks and toolbox. This avoids hardcoding paths and ensures that the latest local version of the test blocks is loaded and used.
I also updated the
npm run test:browsercommand to build the plugin, rather than implicitly relying on that having been done.Reason for Changes
These tests have caught some bugs before, so it's useful to have them enabled.
Test Coverage
Is better.