Tests: Assert unsupported requests for edit site export controller

[shail-mehta]

Part of: #66073

What

Replaces empty @doesNotPerformAssertions get/create/update/delete stubs in Tests_REST_WpRestEditSiteExportController with real negative assertions.

Each unsupported request asserts rest_no_route with status 404, using an authenticated administrator.

Updated file: tests/phpunit/tests/rest-api/wpRestEditSiteExportController.php

Why

The edit site export controller only registers GET /wp-block-editor/v1/export. Empty abstract-method stubs hide whether unsupported operations are actually rejected, and the annotation count keeps growing.

This continues the agreed approach from [64004] / [64075] / [64076] on another conventional read-only controller, before any broader WP_Test_REST_Controller_Testcase change.

How

• GET /wp-block-editor/v1/export/example → rest_no_route / 404 (no item route)
• POST /wp-block-editor/v1/export → rest_no_route / 404 (route is GET-only)
• POST / PUT / PATCH /wp-block-editor/v1/export → rest_no_route / 404 (asserts OPTIONS 200 first so the path is proven valid)
• DELETE /wp-block-editor/v1/export → rest_no_route / 404 (asserts OPTIONS 200 first)
• Uses OPTIONS instead of GET to prove the route: a successful GET triggers the ZIP export and exits the request
• Left test_get_items() annotated (export GET is not a collection list operation)
• Left prepare_item() / get_item_schema() unchanged (held for further discussion)
• Did not change the abstract base class yet

Testing instructions

1. Start the local WordPress develop environment.
2. Run: npm run test:php -- --filter Tests_REST_WpRestEditSiteExportController

Use of AI tools

Cursor

[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 shailu25, lancewillett.

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

[lancewillett]

Optional follow-up, not required before landing: alongside the OPTIONS status assertions, assert $this->assertSame( $route, $response->get_matched_route() );. rest_handle_options_request() returns a default 200 response even when no route matches, so status alone does not prove the export route exists. The existing route-registration test provides coverage, making this a small strengthening of these checks.

_{AI review · gpt-6}

[lancewillett]

PR #14115 landed in https://core.trac.wordpress.org/changeset/64275