Skip to content

7.1 Branch: Build/Test Tools: Remove script to run Gutenberg E2E tests in Core. - #15930

Draft
desrosj wants to merge 1 commit into
WordPress:7.1from
desrosj:backport/65309-7.1
Draft

desrosj wants to merge 1 commit into
WordPress:7.1from
desrosj:backport/65309-7.1

Conversation

@desrosj

@desrosj desrosj commented Nov 12, 2026

Copy link
Copy Markdown
Member

Backports r65309 and r65417 to the 7.1 branch.

Removes tests/gutenberg/run.js and tests/gutenberg/.wp-env.sample.json, along with the chalk and uuid dev dependencies, which were only used by that script. No other script, Grunt task, or workflow in this branch references tests/gutenberg, and nothing else in the branch's tooling imports chalk or uuid.

The chalk and uuid entries were removed from package-lock.json.

Trac ticket: https://core.trac.wordpress.org/ticket/65845

Use of AI Tools

Claude Code (Claude Opus 5.5) applied the trunk change to each branch and opened this PR. package-lock.json was regenerated with Node 20 / npm 10 (the version this branch's engines field specifies) using npm install --package-lock-only. The diff was checked to contain only deletions.

🤖 Generated with Claude Code

In [48382] a script was added to run the Gutenberg end-to-end tests in `wordpress-develop`. Besides a few small changes related to normal Gutenberg syncs, these files have not been touched since being introduced and the script no longer works.

It was never formally added to any GitHub Actions workflows.

Removing this script also allows the `chalk` and `uuid` dependencies to be removed. "And another one gone, and another one gone."

Merges [65309] and [65417] to the 7.1 branch.

See #65845, #50469, #59407.
@desrosj desrosj self-assigned this Nov 12, 2026
@github-actions

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant