Skip to content

Tests: Unregister custom post types in getDeletePostLink.php - #15106

Closed
rejaulalomkhan wants to merge 1 commit into
WordPress:trunkfrom
rejaulalomkhan:tests/65893-isolate-link-getdeletepostlink
Closed

rejaulalomkhan wants to merge 1 commit into
WordPress:trunkfrom
rejaulalomkhan:tests/65893-isolate-link-getdeletepostlink

Conversation

@rejaulalomkhan

Copy link
Copy Markdown

Description

In tests/phpunit/tests/link/getDeletePostLink.php, register_post_type() is used across tests (test_get_delete_post_link_returns_null_for_unregistered_post_type and test_get_delete_post_link_custom_post_type) to register custom post types 'cpt_unreg_test' and 'cpt_delete_test'.

While the tests attempt inline unregistration, any early test failure or exception leaves these post types registered in the global $wp_post_types array, leaking state into subsequent test classes.

This PR adds cleanup for both 'cpt_unreg_test' and 'cpt_delete_test' in Tests_Link_GetDeletePostLink::tear_down(), ensuring complete test isolation.

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


This pull request modifies test files only.

Summary of Changes

  • Added unregistration of 'cpt_unreg_test' and 'cpt_delete_test' in Tests_Link_GetDeletePostLink::tear_down() in tests/phpunit/tests/link/getDeletePostLink.php.

Test Coverage

  • Verified locally via vendor/bin/phpunit --filter Tests_Link_GetDeletePostLink (12 tests, 17 assertions: all passed).
  • Ran PHPCS via vendor/bin/phpcs tests/phpunit/tests/link/getDeletePostLink.php (0 errors, 0 warnings).

Use of AI Tools

  • Tool: Antigravity
  • Model: Gemini 2.5 Pro
  • Scope: Identifying test isolation leaks in getDeletePostLink.php and drafting teardown cleanup.

@github-actions

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.

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

Props rejaulalomkhan.

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


Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

  • @propsbot add <username> to give props to a GitHub user. Requires write access.
  • @propsbot remove <username> to leave a user out of the props. Requires write access.
  • @propsbot refresh to refresh this list. Adding the props-bot label works too.

@lancewillett

Copy link
Copy Markdown
Member

The added cleanup for cpt_unreg_test, cpt_delete_test repeats the Core test harness’s registry reset before each test. These registrations do not opt out of that reset, and no existing consumer is shown to fail before it. Closing this cleanup-only proposal as redundant; the existing behavioral tests remain unchanged.

The inherited reset runs in WP_UnitTestCase_Base::set_up().

Thanks for working on test isolation. We can reopen this if an existing test or fixture fails without the cleanup and passes with it under the same environment and order.

AI review · gpt-6

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.

3 participants