[tests] Cut product export E2E from 4 titles to 1, moving the export screen to PHPUnit - #68649

Submission Review Guidelines:

• I have followed the WooCommerce Contributing Guidelines and the WordPress Coding Standards.
• I have checked to ensure there aren't other open Pull Requests for the same update/change.
• I have reviewed my code for security best practices.
• I have assessed the impact of this change and followed the applicable review requirements.
• Following the above guidelines will result in quick merges and clear and detailed feedback when appropriate.

Changes proposed in this Pull Request:

Three of the four product export browser titles were checking what the export screen renders when you arrive from the product list with a selection: which products it lists, where the clear link points, and what it shows when nothing is selected. That is a view assertion, and a view is cheaper and more precisely testable from PHP than through wp-admin. Those three move down a layer; the one that genuinely needs a browser stays.

Refs TESTOPS-288

Part of the #68046 split.

The retained title, preserves multiple selection through export and clear, is the one no lower layer can replace: it starts on the product list, carries a real selection across a navigation, and then clears it.

No test here reads an actual CSV file, and none did before

Worth stating plainly, because "product export" suggests otherwise. Neither the removed browser titles nor the new PHP tests ever generate a CSV and read its bytes. The old titles asserted button text, hrefs and screen copy; the new tests assert the rendered view and the exporter's in-memory row set. product-export.spec.ts has no download handling at all — the only specs in the suite that wait on a download are analytics.spec.ts and customer-list.spec.ts.

So this batch moves assertions sideways, from the browser to PHP. It does not deepen coverage of the export mechanism, and the gap in end-to-end CSV file coverage is pre-existing and untouched.

The one real loss: the product list's export button

The Export N selected button on the product list is written by jQuery (client/legacy/js/admin/woocommerce_admin.js), not by the view this batch tests, so no PHP test can reach it.

The singular case is less of a loss than it first looks. The button text is a single string with %d substituted — woocommerce_admin.strings.export_selected_products.replace( '%d', count ) — with no separate singular branch, so Export 1 selected and Export 2 selected travel the same code path, and the retained title still exercises it with two products.

What is genuinely unverified now is the other branch: restoring the button's original text and href when the last checkbox is unchecked. Nothing covers that any more.

This file had moved on trunk, and the branch's version was not taken blind

class-wc-product-csv-exporter-test.php gained a method on trunk after this work branched: #68567 added test_export_row_for_product_loaded_before_its_global_attribute_is_deleted. Checking out the migration branch's copy wholesale would have deleted it.

Instead trunk's file was kept and only this branch's method re-applied on top. The result is checkable rather than asserted: both methods are present, the file's diff against trunk has zero deleted lines, and the class goes from 5 tests to 6.

Screenshots or screen recordings:

Not applicable. Test-only change.

How to test the changes in this Pull Request:

1. Check out this branch and run pnpm install --frozen-lockfile from the repository root.
2. Start the PHPUnit environment: pnpm --filter=@woocommerce/plugin-woocommerce env:test.
3. Run the two PHP classes with anchored filters. Anchoring matters: a sibling class WC_Tests_Product_CSV_Exporter exists, and PHPUnit's --filter is an unanchored substring regex, so a loose filter runs more than it claims.
   • pnpm --filter=@woocommerce/plugin-woocommerce test:php:env -- --filter '/^WC_Product_CSV_Exporter_Test::/' — expect OK (6 tests, 32 assertions).
   • pnpm --filter=@woocommerce/plugin-woocommerce test:php:env -- --filter '/^WC_Admin_Product_Export_View_Test::/' — expect OK (2 tests, 21 assertions).
4. Start the E2E environment: pnpm --filter=@woocommerce/plugin-woocommerce env:e2e.
5. Run the spec with retries disabled: pnpm --filter=@woocommerce/plugin-woocommerce test:e2e:with-env default --project=core-parallel --retries=0 --workers=1 tests/e2e/tests/product/product-export.spec.ts. The retained title should pass; the summary reads 3 passed and 1 skipped, the 3 being that title plus the global authentication and site setup projects.
6. Confirm the new view test detects a real regression in the template. In plugins/woocommerce/includes/admin/views/html-admin-page-product-export.php, find the branch that echoes the hidden product_ids input and change its if ( $is_exporting_product_ids ) { to if ( false ) {. Re-run the first command in step 3 and expect test_selected_products_render_exact_export_state to fail with Failed asserting that null is identical to '10'.. Revert.
7. Confirm the exporter test detects a scoping regression. In plugins/woocommerce/includes/export/class-wc-product-csv-exporter.php, in prepare_data_to_export, change $args['include'] = $this->product_ids_to_export; to $args['include'] = array();. Re-run the first command in step 3 and expect test_selected_product_ids_restrict_export_rows to fail on an array-identity assertion, admitting an unrelated product and omitting the selected variations. Revert.
8. Confirm the retained browser title still guards the clear link. In the same view file, change $clear_url = remove_query_arg( 'product_ids' ); to $clear_url = add_query_arg( 'product_ids', implode( ',', $product_ids_to_export ) );. Re-run step 5 and expect a failure reading Expected substring: not "product_ids=", with the URL still carrying the selected IDs. Revert.

Testing that has already taken place:

Everything below ran on this branch against a local WordPress, with retries disabled and one worker. Trunk was at adefb5f971.

• Baseline first. Trunk's copy of the spec ran green before extraction (4 titles), and trunk's WC_Product_CSV_Exporter_Test was OK (5 tests, 29 assertions) under the anchored filter. So the environment was known good and the merge result is measured against a real starting point.
• Extraction. The spec and the new view test are byte-identical to the migration branch. The exporter test is deliberately not: it is trunk's file plus this branch's one method, verified additive.
• Retained title. Green at --retries=0 --workers=1.
• Lower layer. WC_Product_CSV_Exporter_Test OK (6 tests, 32 assertions); WC_Admin_Product_Export_View_Test OK (2 tests, 21 assertions).
• Mutation re-check, all 3 behavior families. One recorded mutation per family, each turning its focused command red at the assertion the mutation matrix names, each reverted and green again: the view's hidden-input branch, the exporter's include scoping, and the view's clear-link URL.
• Lint. lint:changes:branch exits 0 with one pre-existing warning and no errors. oxlint attributes no new finding to the change.
• PHPStan: not applicable, and checked rather than assumed. phpstan.neon scopes to woocommerce.php, src/ and includes/; this batch touches only tests/.
• Identifier sweep. No internal campaign identifiers in any of the three paths, with a detector proven against a file where such identifiers do exist.

Milestone

• Automatically assign milestone for the next WooCommerce version

Note: Check the box above to have the milestone automatically assigned when merged.
Alternatively (e.g. for point releases), manually assign the appropriate milestone.

Changelog entry

• Automatically create a changelog entry from the details below.

• This Pull Request does not require a changelog entry. (Comment required below)

Use of AI Tools

The migration was produced by an agent-run campaign with per-test mutation verification (see #68046). This PR was assembled, verified in isolation, and reviewed by an agent; the author reviewed the diff and takes responsibility for it.

🤖 Generated with Claude Code