test: migrate and explain custom server deploy exclusions (#98994)
## Summary Custom-server suites depend on local server entrypoints that deploy mode does not launch. Replace their legacy `skipDeployment` exclusions and `skipped` returns with `@force-gate !deploy` and explain the dependency, while preserving their existing local mode restrictions and assertions. This covers six test files, including the custom-server sections of API body parsing and OpenTelemetry. The ordinary API JSON body-parser case remains enabled in deploy mode; only the Express pre-parsing cases are excluded. The custom-server shutdown suite also requires the runner to signal its server process and observe `after()` completion. Stack: #99012 → #98994 → #99392 → #98911. Based on #99012; #99392 separately explains local process-control exclusions. ## Verification - The two added suites passed in both webpack development and production modes: five tests in each mode. - Collection with the real gate runtime and fixture setup stubbed confirmed all five tests enabled locally, and only the ordinary API body-parser test enabled in deploy mode. Both parameterized shutdown signals are excluded in deploy. - All 24 gate-transform tests passed. Formatting and ESLint passed for the added files. - The JavaScript workspace build passed. The full bootstrap build failed in the native Rust step (`cargo metadata failed to run`). - No new deployment was created. The ordinary API body-parser case passed in the earlier deployment experiment. <!-- NEXT_JS_LLM -->
Showing
Please
register
or
sign in
to comment