Skip to content

Tests: Unregister custom post type in getTheAuthorPosts.php - #15093

Open
rejaulalomkhan wants to merge 1 commit into
WordPress:trunkfrom
rejaulalomkhan:tests/65893-isolate-user-gettheauthorposts
Open

rejaulalomkhan wants to merge 1 commit into
WordPress:trunkfrom
rejaulalomkhan:tests/65893-isolate-user-gettheauthorposts

Conversation

@rejaulalomkhan

Copy link
Copy Markdown

Description

In tests/phpunit/tests/user/getTheAuthorPosts.php, register_post_type() is used in test_get_the_author_posts_with_custom_post_type() to register a custom post type 'wptests_pt'.

While the test calls _unregister_post_type() inline at the end of the method, an assertion failure before that point leaves 'wptests_pt' registered in the global $wp_post_types array, leaking state into subsequent tests.

This PR adds a tear_down() method in Tests_User_GetTheAuthorPosts to unregister 'wptests_pt' using unregister_post_type(), ensuring complete test isolation.

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


This pull request modifies test files only.

Summary of Changes

  • Added tear_down() method in Tests_User_GetTheAuthorPosts within tests/phpunit/tests/user/getTheAuthorPosts.php unregistering 'wptests_pt'.

Test Coverage

  • Verified locally via vendor/bin/phpunit --filter Tests_User_GetTheAuthorPosts (5 tests, 8 assertions: all passed).
  • Ran PHPCS via vendor/bin/phpcs tests/phpunit/tests/user/getTheAuthorPosts.php (0 errors, 0 warnings).

Use of AI Tools

  • Tool: Antigravity
  • Model: Gemini 2.5 Pro
  • Scope: Identifying test isolation leaks in getTheAuthorPosts.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.

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