Remove phpunit tests for features backported to Core

[youknowriad]

What?

There are some features that start in Gutenberg and make their way into Core and eventually their code gets removed from Gutenberg. For these features, we generally unit test them within the plugin but when the code makes its way into Core (with its tests), there's no need to keep the tests in Core anymore. This PR just removes some of these old tests that are not relevant for the Gutenberg plugin anymore.

cc @WordPress/gutenberg-core

[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.

Core SVN

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

Props youknowriad, gziolo, jsnajdr, ntsekouras, ramonopoly, andraganescu.

GitHub Merge commits

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: youknowriad <youknowriad@git.wordpress.org>
Co-authored-by: gziolo <gziolo@git.wordpress.org>
Co-authored-by: jsnajdr <jsnajdr@git.wordpress.org>
Co-authored-by: ntsekouras <ntsekouras@git.wordpress.org>
Co-authored-by: ramonjd <ramonopoly@git.wordpress.org>
Co-authored-by: draganescu <andraganescu@git.wordpress.org>

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

[youknowriad]

This function is not in Gutenberg anymore. cc @getdave for confirmation. Let's also confirm that the tests were backported properly.

[getdave]

They have been removed from Gutenberg compat now I believe yes 👍

[youknowriad]

This function is not in Gutenberg anymore. cc @ntsekouras @ramonjd for confirmation. Let's also confirm that the tests were backported properly.

[ntsekouras]

The ones I had added have been backported: WordPress/wordpress-develop#3221

[youknowriad]

This function is not in Gutenberg anymore. cc @aaronrobertshaw for confirmation. Let's also confirm that the tests were backported properly.

[aaronrobertshaw]

Thanks for the ping 👍

I can confirm wp_get_block_css_selector is now only defined in core. This test was also backported in WordPress/wordpress-develop#4655 and the corresponding file in core still matches the test file being removed in this PR.

[youknowriad]

This function is in Core now. cc @gziolo for confirmation. Let's also confirm that the tests were backported properly.

[gziolo]

This class is testing the code that's bridging the gaps between WP core and Gutenberg. We can remove it unless @ockham plans to apply any changes in the compat layer.

[youknowriad]

If I'm not wrong, the test hasn't been touched since 6.4 which means, that if we want to make any changes now, we'll have to do add a file to 6.5 folder and modify this file. It seems actually better to remove it that way, it clarifies for the implementor what part of the test need to be backported to Core for the "new" changes.

I can restore it though, just wanted to explain my reasoning here.

[gziolo]

Sounds like a good reasoning 👍🏻

[github-actions]

Flaky tests detected in d0ff985.
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/7826385965
📝 Reported issues:

• [Flaky Test] aria-disabled is correctly hydrated for different values #54370 in /test/e2e/specs/interactivity/directive-bind.spec.ts

[draganescu]

This looks good according to my knowledge of what has been landed in core.