[devmuhib009]

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

This PR removes redundant mid-test _unregister_post_type() calls in Tests_Comment_Query, as tear_down() already cleans up the custom post types via unregister_post_type().

[github-actions]

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 devmuhib, lancewillett.

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]

Thanks, @devmuhib009. Holding this one for now, along with the rest of this series; see https://core.trac.wordpress.org/ticket/65893#comment:656 for why.

_{AI review · claude-opus-5-5}

[Copilot]

🟢 Approval recommended

No active review issues were identified for the removal of redundant post-type cleanup from two comment query tests.

No open issues 🎉

What changed in this PR

This PR simplifies Tests_Comment_Query cleanup by relying on the existing tear_down() method to unregister custom post types.

Changes:

• Removes redundant _unregister_post_type() calls from test_post_type_single_value() and test_post_type_singleton_array().
• Leaves test assertions and production code unchanged.

File	Description
tests/​phpunit/​tests/​comment/​query.php	Removes duplicate post type cleanup from two comment query tests.

_{Review effort: Balanced}

[lancewillett]

Revisited the hold from #65893 comment 656. Both removed pairs of unregister calls follow their final assertion; they are not part of either scenario. The custom post types have no automatic-reset opt-out. On current trunk, inherited setup resets them before each Core test; the local teardown mentioned in the description has since been removed. Please update that explanation when convenient.

The four-class comparison passes 197 tests / 573 assertions before and after in single site and multisite (random seed 65893). Explicit class-boundary ordering also passes 10 tests / 66 assertions: each changed comment test ends its class before the existing hierarchical-slug test runs. That consumer registers its own types after inherited setup. No tests or assertions are removed, and no runtime improvement is claimed.

_{AI review · gpt-6}

[lancewillett]

PR #15498 landed in https://core.trac.wordpress.org/changeset/65397