Files
reverse-engineering-anything/tests/boundary/browser/browserFixtureHttpTargets.test.ts
T
84990f9777 test: remove fixed child-process deadlines from tests
239 literal timeoutMs values on cli.run and processes.run only restated
a guess at host speed. On hosted runners with four workers, cliOutput's
3-second value failed while the command still produced correct output.
Deadlines that are the behavior under test, derived from an operation
budget, or that bound a regression's wait remain.

Co-Authored-By: gensokyo-dev <342580529+gensokyo-dev@users.noreply.github.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 13:21:13 +08:00

28 lines
865 B
TypeScript

import { fileURLToPath } from "node:url";
import { expect } from "vitest";
import { processTest } from "../../support/process/processFixture.js";
for (const kind of ["proxy", "workers", "storage"] as const) {
processTest(
`${kind} HTTP fixture preserves targets and survives invalid requests`,
async ({ processes }) => {
const result = await processes.run(process.execPath, [
fileURLToPath(
new URL(
"../../fixtures/browserFixtureHttpTargets.mjs",
import.meta.url,
),
),
kind,
]);
expect(result.signal, result.stderr).toBeNull();
expect(result.exitCode, result.stderr).toBe(0);
expect(result.stderr).toBe("");
expect(result.stdout).toBe(
`${kind}: target routing, invalid-target recovery and physical close passed\n`,
);
},
);
}