cli/apps/cli-e2e/tests · cli23/cli

GGitHubtest(cli-e2e): cover the replay server with effect lint (CLI-2880) (#7387)

Files	Last commit	Last update
provided-context.ts	test(cli): collocate live e2e coverage (#6294) ## Summary Collocate remote-platform golden-path tests beside the commands they cover in apps/cli, while keeping Docker-stack-only scenarios as ordinary e2e tests and leaving the apps/cli-e2e replay and recording suite unchanged. Use one serial live Vitest project with a single extended test fixture. Global setup requires a Management API URL and access token, provisions one disposable project through the typed Effect API client, waits with bounded retry semantics, derives the platform tenant host from project metadata, and shares cli plus project fixtures with every test. Explicit live runs fail fast when configuration is missing; there are no capability gates or runtime skips. Keep live coverage intentionally narrow: one representative golden path per covered command. Setup and teardown may invoke other commands, but assertions stay focused on the command under test. Exact owned resources are cleaned even after ambiguous command results, and target plus cleanup failures are preserved. Move the eight local Docker-stack suites to e2e naming, including functions dev synchronization on observable reload completion. The standalone live workflow retains Docker preflight, serial execution, one attempt, a 20-minute limit, and scoped project sweeping.	2 months ago
setup.ts	test(cli-e2e): cover the replay server with effect lint (CLI-2880) (#7387) ## TL;DR brings the `apps/cli-e2e` replay server under the effect lint, so the allow list covers the whole ## whats introduced? - the server runs on `FileSystem`, `HttpClient` and typed errors with `Bun.serve` as its only edge, and the global setup owns it through a scope - the docker relay uses the `node:http` client from `@effect/platform-node`, because bun's `fetch` sorts response headers and recorded fixtures keep them in arrival order - replay responses and recorded fixture files stay byte for byte the same ps: in record mode the docker relay can send a response chunked where it used to send `content-length`, with the same body bytes, and a failed relay logs its own error instead of the raw socket error ## ref - closes: CLI-2880	7 days ago
staging-project.ts	test(cli-e2e): cover the e2e harness with effect lint (CLI-2878) (#7384) ## TL;DR brings the `apps/cli-e2e` harness under the effect lint ## whats introduced? - `env.ts` reads the environment through `Config` and passes the record mode and staging url to the global setup instead of rewriting `process.env` - the global setup, staging project helpers, fixture loader, pg mock and vitest config run as effect programs - the fixture loader decodes fixtures through a schema, so a hand written fixture missing a field fails at load with its file name, and every committed fixture decodes unchanged - the replay server stays excluded until the last page of this stack ## ref - related: CLI-2878	7 days ago