Skip to content

Build/Test Tools: Use createMock() in WP_Upgrader tests - #13458

Closed
Soean wants to merge 1 commit into
WordPress:trunkfrom
Soean:tests/wp-upgrader-create-mock
Closed

Build/Test Tools: Use createMock() in WP_Upgrader tests#13458
Soean wants to merge 1 commit into
WordPress:trunkfrom
Soean:tests/wp-upgrader-create-mock

Conversation

@Soean

@Soean Soean commented Sep 9, 2026

Copy link
Copy Markdown
Member

Replace getMockBuilder( $class )->getMock() with the shorter createMock( $class ) in the WP_Upgrader test setup. Neither mock configures constructor arguments or a method list, so the builder adds nothing here, and createMock() is the form already used across the rest of the test suite.

The remaining getMockBuilder() calls in the test suite are left untouched, as they all configure constructor arguments or mocked methods and therefore genuinely need the builder.

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


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.

Replace `getMockBuilder( $class )->getMock()` with the shorter `createMock( $class )` in the `WP_Upgrader` test setup. Neither mock configures constructor arguments or a method list, so the builder adds nothing here, and `createMock()` is the form already used across the rest of the test suite.

`createMock()` additionally disables the original constructor. This is safe for both mocks: `WP_Filesystem_Base` has no constructor, and while `WP_Upgrader_Skin::__construct()` populates `$this->options`, the tests only ever stub methods and never read that property.

The remaining `getMockBuilder()` calls in the test suite are left untouched, as they all configure constructor arguments or mocked methods.
@github-actions

github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props soean.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@lancewillett
lancewillett self-requested a review September 9, 2026 13:31
wporg-sync pushed a commit that referenced this pull request Sep 9, 2026
Use `createMock()` for the upgrader skin and filesystem mocks. These test doubles need no custom builder configuration, original constructor, or cloning behavior.

Developed in: #13458

Props soean.
See #65819.


git-svn-id: https://develop.svn.wordpress.org/trunk@63562 602fd350-edb4-49c9-b593-d223f7449a82
@lancewillett

Copy link
Copy Markdown
Member

wporg-sync pushed a commit to WordPress/WordPress that referenced this pull request Sep 9, 2026
Use `createMock()` for the upgrader skin and filesystem mocks. These test doubles need no custom builder configuration, original constructor, or cloning behavior.

Developed in: WordPress/wordpress-develop#13458

Props soean.
See #65819.

Built from https://develop.svn.wordpress.org/trunk@63562


git-svn-id: http://core.svn.wordpress.org/trunk@62738 1a063a9b-81f0-0310-95a4-ce76da25c4cd
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.

2 participants