Repository navigation
Conversation
…iew test. See #66755.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. Props Bot commandsYou can trigger Props Bot actions by commenting on this PR:
|
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.
Tests_WP_Customize_Widgets::test_customize_preview_enqueue()checks thatWP_Customize_Widgets::customize_preview_enqueue()enqueues thecustomize-previewstyle. Since r39951 (#39498) that style is enqueued byWP_Customize_Manager::customize_preview_init(), and the widgets method only enqueues thecustomize-preview-widgetsscript. The assertion stayed, so it depends on pre-existing global$wp_stylesstate and fails when the test runs alone.Trac ticket: https://core.trac.wordpress.org/ticket/66755
What changes
customize-previewstyle assertion is removed. The script and dependency assertions stay.Testing
Locally with PHP 8.4.27, MySQL 9.7.4 and PHPUnit 9.6.39 on single site and multisite:
vendor/bin/phpunit --filter 'Tests_WP_Customize_Widgets::test_customize_preview_enqueue$': 1 failure on trunk ("Failed asserting that false is true." atwidgets.php:785), OK (1 test, 10 assertions) with this change. Same with-c tests/phpunit/multisite.xml.vendor/bin/phpunit --filter 'Tests_WP_Customize_Widgets::': OK on trunk (28 tests, 410 assertions; the class order masks the stale assertion) and with this change (28 tests, 409 assertions).-c tests/phpunit/multisite.xml --testsuite default --order-by=random --random-order-seed=202.Use of AI Tools
AI assistance: Yes
Tool(s): Claude Code and Codex
Used for: Investigation, code, local testing and PR wording. I reviewed the reasoning, the code and the test results, and I take responsibility for the contribution.
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.