[huzaifaalmesbah]

Description

Adds tests for the row classes and the bulk action checkbox that WP_Plugins_List_Table::single_row() outputs for each plugin. These had no tests; #14598, #14602 and #14603 cover the action links and row meta of the same method.

The tests render a row for a temporary plugin, read the opening tr tag and the checkbox column from the output, and set the dependency state through the static properties of WP_Plugin_Dependencies, which the shared plugin dependencies test case resets. They cover:

• the inactive and active row classes, and the full checkbox markup;
• a disabled checkbox for a plugin with dependents or with unmet dependencies;
• no checkbox and the update class when the plugin's PHP requirement is not met, and a checkbox with the update class when its WordPress requirement is not met;
• the update class only when the plugin has an update and the upgrade view has updates;
• the paused and is-uninstallable classes;
• no checkbox for must-use plugins, which are shown as active;
• on multisite, no checkbox on a site for a network-active or network-only plugin.

Removing or changing each branch of the row classes and checkbox makes at least one test fail on single site or multisite.

This is a test-only change; no production code is modified.

Testing Instructions

1. Run the tests on single site:
   npm run test:php -- --filter Tests_Admin_wpPluginsListTableRowCheckbox
2. Run them on multisite:
   npm run test:php -- --filter Tests_Admin_wpPluginsListTableRowCheckbox -c tests/phpunit/multisite.xml
3. Run them in random order:
   npm run test:php -- --filter Tests_Admin_wpPluginsListTableRowCheckbox --order-by=random
4. Run the plugins group:
   npm run test:php -- --group plugins
5. Run PHPCS on the test file:
   node ./tools/local-env/scripts/docker.js run --rm php ./vendor/bin/phpcs tests/phpunit/tests/admin/wpPluginsListTableRowCheckbox.php

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

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Brainstorming edge-case scenarios and drafting test boilerplate; test architecture, assertions, and local PHPUnit verification were written and validated by me.

[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 Committers: Use this line as a base for the props when committing in SVN:

Props huzaifaalmesbah, mukesh27.

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

[mukeshpanchal27]

The assertions match the source, and CI passes. One note about fixture cleanup inline.

[mukeshpanchal27]

In core tests, WP_PLUGIN_DIR is tests/phpunit/data/plugins, which is a tracked directory. If a run stops partway, such as on a fatal error or Ctrl+C, tear_down() never runs and this fixture folder stays there. The slug comes from a counter that starts at 1 again on the next run, so mkdir() fails on the same folder name. So every test in the class fails here until someone deletes the folder by hand. The leftover also shows up in git status.

Could this helper, or set_up(), remove a leftover folder first? #14600 already does this: its remove_plugin() helper runs in both set_up() and tear_down().

[huzaifaalmesbah]

Good catch, thanks! Added a remove_plugin() helper that clears a leftover folder before mkdir() and in tear_down(), in d8f2c3c. I checked it with a leftover folder in place: the old code failed and the new code passes.