Files
sencho/e2e
Anso 55737ab34d test(stack-files): end-to-end coverage for the file explorer audit surface (#1218)
* test(stack-files): add end-to-end coverage for the file explorer audit surface

Companion to e2e/stack-files.spec.ts, which already pins the basic
admin and community-tier upload/edit/delete/download flows. The new
spec adds the harder-to-reach surfaces the audit flagged:

- Path-traversal corpus on GET /files: nine variants ( .. , ../etc,
  a/../b , absolute POSIX, Windows drive, backslash, double-slash,
  NUL byte, a/./b ) each asserted to return 400 INVALID_PATH.
- Protected-file enforcement via direct API: compose.yaml and .env
  delete return 409 PROTECTED_FILE; a subdirectory entry named
  compose.yaml still deletes (root-scope guarantee preserved).
- Optimistic concurrency: two writers race on the same file via
  If-Match headers; the loser sees 412 PRECONDITION_FAILED with the
  current content payload, and the winner's bytes are on disk.
- Large directory truncation: 1100 entries surface 1000 in the body
  with X-Truncated: true and X-Total-Count headers intact.
- Binary detection and force=text override: a UTF-8 file carrying a
  NUL byte returns binary:true by default and is rescued via
  ?force=text. Oversized files keep the no-inline-content contract
  even when force=text is set.
- 25 MB upload cap: a 25 MB + 1 byte payload trips the multer
  LIMIT_FILE_SIZE branch and returns 413 TOO_LARGE.
- Symlink semantics: DELETE removes only the link entry and leaves
  the target intact; PUT permissions on a symlink returns 409
  LINK_CHMOD_UNSUPPORTED with the target mode unchanged.
- UI lifecycle: upload via the dropzone then API rename, and API
  mkdir; both verify the resulting tree state by reloading the
  Files tab.

Four deferred surfaces are declared as test.skip with a one-line
rationale each: the remote-node matrix and mid-op disconnect
(require a real peer enrolled in CI), the developer-mode diagnostic
matrix (no stable hook for backend stdout in Playwright; covered at
the route-test layer), and the viewer-role tier-persona matrix
(role gating is covered at the route-test layer).

* test(stack-files): trim memory-heavy cases out of the E2E spec

CI ran the spec end-to-end and the run completed, but the two heaviest
cases (1100-file directory seed and a 25 MB upload buffer) pushed the
single-worker Playwright queue past the dashboard-render budget for
the specs that followed. stack-files.spec.ts and stacks.spec.ts saw
their loginAs await time out at 10 s while the post-spec sidebar was
still loading.

Both behaviours are exercised at the backend route-test layer
(stack-files-routes.test.ts pins the 1000-entry truncation header on
a 1100-file directory and the multer LIMIT_FILE_SIZE 413 with a 26 MB
buffer), so deleting them from the E2E spec loses nothing material.
The oversized force=text test is also trimmed from 2.5 MB to 2.1 MB,
which still exercises the >2 MB branch on the backend.

The deferred-coverage block now lists the two excised cases with the
rationale for why E2E is the wrong layer for them.

* test(stack-files): collapse 7 per-describe seed hooks into 1 file-scope pair

Each inner describe previously ran its own seedSuite + teardownSuite
pair: 7 logins, 7 stack creates, 7 stack deletes, all serial. That
added 15-20 seconds of CI setup overhead on a single-worker run and
pushed the post-spec dashboard load past the 10 s budget some
downstream specs allow on their loginAs await.

Moving the seed/teardown to file scope keeps the test stack present
for every test in this file with one fixture pair. Each test still
calls loginAs in its beforeEach so the page state is fresh, but the
expensive setup runs once instead of seven times.
2026-05-25 09:56:56 -04:00
..