[sirreal]

What?

Follow-up to #72236.

Updates background block support PHP tests to compare generated wrapper markup with assertEqualHTML() instead of byte-for-byte string equality. Also enables the PHP unit test workflow to run against the previous major WordPress version on PRs.

Why?

Equivalent HTML can serialize with different character references across WordPress versions, for example ' vs '. These differences should not fail tests when the resulting HTML is semantically equivalent.

How?

• Replaces assertEquals() with assertEqualHTML() for HTML semantic equality comparison instead of string equality.

Testing Instructions

CI workflow should be sufficient. This is a testing change.

Use of AI Tools

OpenAI Codex was used to help rebase the branch, resolve conflicts, run local checks, and draft this PR description. The original changes were authored without the use of AI.

[github-actions]

Flaky tests detected in 95c87ef.
Some tests passed with failed attempts. The failures may not be related to this commit but are still reported for visibility. See the documentation for more information.

🔍 Workflow run URL: https://github.com/WordPress/gutenberg/actions/runs/27605304690
📝 Reported issues:

• [Flaky Test] shouldn't conflict with server-side autosave #78706 in /test/e2e/specs/editor/various/autosave.spec.js

[github-actions]

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.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: sirreal <jonsurrell@git.wordpress.org>
Co-authored-by: ntsekouras <ntsekouras@git.wordpress.org>

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

[ntsekouras]

Thanks for the PR! I thought we had tried that before when investigating and the CI didn't pass. Wasn't that the case?

CI passes.

The difference between now and back then is that the previous failures were from PHP previous major version, which as of #72506 they are not run on GB PR before merged. Have you tested those jobs somehow?

[sirreal]

The difference between now and back then is that the previous failures were from PHP previous major version, which as of #72506 they are not run on GB PR before merged. Have you tested those jobs somehow?

Thank you for noticing that! Indeed, the test method was unavailable in the previous version and we see an error:

Error: Call to undefined method WP_Block_Supports_Background_Test::assertEqualHTML()

This change would be good to make but unfortunately we'll have to wait 🙂

[sirreal]

assertEqualHTML should be available now and can be used. It's been available since 6.9.