Beautiful, AI-native markdown IDE and LLM wiki
TypeScript 2nd-brainagent-skillsclaudecodexcompany-braindocsknowledge-knowledge-baseknowledge-managementllmllm-wikillm-wiki-karpathymarkdownmarkdown-editormdmdxnotespkmsecond-brainskills
import { defineConfig } from '@playwright/test';
import { ONE_LAUNCH_AND_ITS_READINESS_VERDICT_MS } from './tests/smoke/_helpers/launch-desktop';
/**
* Packaged-app Playwright config — the release-gate tier.
*
* Runs a deliberately small subset of the SAME smoke files as
* `playwright.config.ts`, but against a packaged `.app` bundle selected via
* `OK_DESKTOP_PACKAGED_APP` (see `tests/smoke/_helpers/launch-desktop.ts`).
* Two configs, one set of test files.
*
* Why a separate file rather than a `projects` array on the existing config:
* introducing projects changes `testInfo.project.retries` resolution, which
* `tests/smoke/_helpers/electron-stderr.ts` reads to decide whether to attach
* main-process stderr. The required `desktop-smoke` check must keep behaving
* exactly as it does today, so it keeps its own config untouched.
*
* No `globalSetup`: the unpackaged config's stale-build guard compares `src/`
* against `out/`, neither of which describes a packaged bundle — running it
* here would fail on a perfectly good DMG.
*/
/* WARN: desktopLaunchOptions sets OK_IDLE_SHUTDOWN to
PACKAGED_SMOKE_SERVER_IDLE_SHUTDOWN_MS on every packaged launch, so a spec
added here must never leave its server without a /collab client that long. */
/**
* The FR5a subset: launch, project creation, and first-launch MCP wiring. This
* is the smallest set that proves a DMG boots, reaches the renderer, and can
* complete the first-run flow. Widening or narrowing it is a deliberate act —
* `tests/unit/playwright-packaged-config.test.ts` pins the list.
*
* `cold-single-file-launch.e2e.ts` is here because it is packaged-ONLY in a
* stronger sense than the rest: it starts the app through Launch Services
* rather than launching Electron itself, so there is no unpackaged shape of it
* to run. It is the only tier that observes the cold Apple-Event boot path.
*/
export const PACKAGED_SMOKE_SUBSET = [
'cold-single-file-launch.e2e.ts',
'consent-dialog.e2e.ts',
'create-new-project.e2e.ts',
'mcp-wiring.e2e.ts',
] as const;
/**
* Distinct filename so one directory can hold both tiers' JSON reports. The
* reports still SHARE `test-results/`; only the per-test artifact trees are
* separated, by `outputDir` below.
*/
export const PACKAGED_JSON_REPORT_PATH = 'test-results/desktop-smoke-packaged-results.json';
export default defineConfig({
testDir: './tests/smoke',
// Without this, the tier would default to the unpackaged run's
// `test-results/` and clear it at run start, taking that run's per-test
// artifacts with it — Playwright 1.63.0, re-verify on any upgrade, not just
// a major, since the range admits minors and this is undocumented behavior
// of a public API.
//
// That was never reachable: a captured main-process stderr file exists only
// when the smoke FAILED, a failing smoke fails its step, and this tier
// carries no `if:` — so it skips exactly when there is something to lose.
// The safety was that `if:` and nothing else, and one `if: !cancelled()`
// here would have put a failing smoke's only evidence behind a clear. A
// separate tree makes it structural instead of conditional.
//
// Only the artifact trees separate. A reporter's `outputFile` is its own
// path — same 1.63.0 measurement, same re-verify-on-any-upgrade — so
// `PACKAGED_JSON_REPORT_PATH` still lands in `test-results/` beside its
// sibling, and nothing clears it now: fine on a fresh CI workspace, worth
// knowing on a reused one. Both trees upload on failure.
outputDir: 'test-results-packaged',
testMatch: PACKAGED_SMOKE_SUBSET.map((file) => `**/${file}`),
// Matches the unpackaged config's CI budget. A packaged launch is if anything
// slower than `electron out/main/index.js` (Gatekeeper assessment, first-run
// dyld cache warm-up), so a tighter budget would only add flake.
timeout: process.env.CI ? 150_000 : ONE_LAUNCH_AND_ITS_READINESS_VERDICT_MS,
retries: process.env.CI ? 2 : 0,
failOnFlakyTests: false,
workers: 1,
fullyParallel: false,
// `json` is what the driver parses for its verdict; `list` keeps the CI log
// readable. No `html` — nothing uploads a report for this tier.
reporter: [['list'], ['json', { outputFile: PACKAGED_JSON_REPORT_PATH }]],
use: {
trace: 'retain-on-failure',
},
});