Files
clean-architecture-frontend…/tests/unit/service-worker-build-output.test.ts
T
DongHyeonka 37e5f9d682 test(e2e): SW spec이 이미 켠 worker와 생성된 사전 캐시 목록을 쓴다 (0929/11-03)
SW e2e는 템플릿의 `= null;` 줄만 바꿔 worker를 켰다. 제품이 이미 ACTIVE로
켠 트리에서는 2건이 실패하고 4건이 실행되지 않았다. 사전 캐시 목록도
템플릿 기준으로 고정돼 있어 해시 파일을 더하면 2건이 실패했다.

선택을 지금 값과 상관없이 고치되, 이미 ACTIVE면 제품의 handler를 그대로
두는 `turnOnServiceWorker` 하나로 모았다. 빌드가 만든 사전 캐시 목록을
`precached`로 돌려주고 spec이 그 목록과 비교한다. 같은 문제를 고친
0929/06-04(`96a4f68`)의 `selectActiveServiceWorker`는 ACTIVE 선택을
템플릿 값으로 덮어써 제품 handler가 빠지므로 이 함수로 바꿨고, 실패한
준비 단계에서 임시 복사본을 지우는 처리는 유지했다(두 브랜치 병합 때
오케스트레이터가 충돌을 풀었다).

위험: 테스트 도우미만 바뀐다. 0929/06-04 단위 테스트의 기대값이 "ACTIVE
선택도 템플릿 값으로 덮어쓴다"에서 "ACTIVE 선택은 그대로 둔다"로 바뀐다.
검증: ACTIVE 선택과 해시 파일 추가 트리 모두 6 passed(에이전트).
병합 뒤 service-worker-build-output 단위 테스트 5/5, SW e2e chromium·webkit
12/12, tsc(test), eslint 통과.
2026-11-01 23:20:28 +09:00

137 lines
4.7 KiB
TypeScript

import { access, mkdir, mkdtemp, readFile, rm, writeFile } from "node:fs/promises";
import { tmpdir } from "node:os";
import path from "node:path";
import { afterAll, beforeAll, describe, expect, it } from "vitest";
import { generateRuntimeConfig } from "../../scripts/generate-runtime-config.ts";
import {
type FixtureBuilds,
prepareFixtureBuilds,
removeFixtureBuilds,
} from "../e2e/support/fixture-builds.ts";
import {
ACTIVE_VALUE,
turnOnServiceWorker,
} from "../e2e/support/service-worker-builds.ts";
/**
* 0929/06-01. Step 6 of `scripts/build-frontend.ts`, the Service Worker Vite
* build, must not change the app output. Vite copies `public/` into `outDir`
* unless the config turns it off, so the worker build replaced the profile
* `dist/config.json` from step 4 with `public/config.json` (local, demo auth,
* loopback API, root release manifest). The build and `verify-release` passed;
* only release admission refused it.
*
* The defect is in how two Vite runs share `dist`, not in one function, so this
* runs the real build over a temp copy with the worker on (one build, ~2s).
* A check of `publicDir === false` on the config object would only restate the
* fix, and the config cannot load without the inputs step 5 generates.
*/
const PROFILE = Object.freeze({
APP_PROFILE: "production",
VITE_ROUTER_BASE_PATH: "/app/",
});
// prepareFixtureBuilds sets VITE_BUILD_ID and RELEASE_ID to `<prefix>-<name>`.
const BUILD_ID = "sw-profile-active";
let builds: FixtureBuilds<"active"> | undefined;
beforeAll(async () => {
builds = await prepareFixtureBuilds("sw-profile", [
{
name: "active",
env: PROFILE,
edit: turnOnServiceWorker,
},
]);
}, 180_000);
afterAll(async () => {
await removeFixtureBuilds(builds);
});
describe("Service Worker build output (0929/06-01, 0929/06-02)", () => {
it("keeps the profile runtime config step 4 wrote", async () => {
const dist = builds!.dist.active;
// The worker build really ran; otherwise nothing below tests step 6.
await access(path.join(dist, "service-worker.js"));
const shipped: unknown = JSON.parse(
await readFile(path.join(dist, "config.json"), "utf8"),
);
expect(shipped).toEqual(
await generateRuntimeConfig("production", {
...process.env,
...PROFILE,
VITE_BUILD_ID: BUILD_ID,
RELEASE_ID: BUILD_ID,
}),
);
});
// 0929/06-02. Under /app/ the worker must precache /app/assets/... and know
// /app/config.json; root URLs 404 at install and the worker never installs.
it("gives the worker URLs under the router base path", async () => {
const generated = (await import(
path.join(
builds!.root,
".generated/frontend-runtime/service-worker-assets.ts",
)
)) as { SERVICE_WORKER_ASSETS: { assets: readonly { url: string }[] } };
const urls = generated.SERVICE_WORKER_ASSETS.assets.map((asset) => asset.url);
expect(urls.length).toBeGreaterThan(0);
expect(urls.filter((url) => !url.startsWith("/app/assets/"))).toEqual([]);
const worker = await readFile(
path.join(builds!.dist.active, "service-worker.js"),
"utf8",
);
// Property names survive minification; the quote style does not.
expect(
/runtimeConfigUrl:\s*["'`]([^"'`]*)["'`]/u.exec(worker)?.[1],
).toBe("/app/config.json");
});
});
// 0929/06-04, 0929/11-03. The worker fixtures must also run in a product that
// already ships the worker: an inactive selection is turned on, and an ACTIVE
// one is kept so the specs exercise that product's own handlers.
describe("turnOnServiceWorker (0929/06-04, 0929/11-03)", () => {
const productActive = `{
mode: "ACTIVE",
scriptPath: "service-worker.js",
handlers: ["PWA_STATIC_ASSETS", "OFFLINE_SYNC_WAKEUP"],
}`;
it.each([
["null", "null", ACTIVE_VALUE],
[
"REMOVE_REGISTRATION",
`{
mode: "REMOVE_REGISTRATION",
scriptPath: "service-worker.js",
}`,
ACTIVE_VALUE,
],
["ACTIVE", productActive, productActive],
])("turns a %s selection on", async (_label, value, expected) => {
const root = await mkdtemp(path.join(tmpdir(), "sw-select-"));
try {
const file = path.join(
root,
"src/features/installed-runtime-capabilities.ts",
);
await mkdir(path.dirname(file), { recursive: true });
const around = (selection: string) =>
`const WEB_WORKERS = Object.freeze([]);\n\nconst SERVICE_WORKER: InstalledServiceWorkerSelection | null = ${selection};\n\nconst OFFLINE_COMMANDS: X | null = null;\n`;
await writeFile(file, around(value));
await turnOnServiceWorker(root);
expect(await readFile(file, "utf8")).toBe(around(expected));
} finally {
await rm(root, { recursive: true, force: true });
}
});
});