Skip to content

test(daemon): strengthen Vela workspace billing coverage - #6304

Closed
AmyShang-alt wants to merge 1 commit into
mainfrom
codex/vela-daemon-regression-coverage
Closed

test(daemon): strengthen Vela workspace billing coverage#6304
AmyShang-alt wants to merge 1 commit into
mainfrom
codex/vela-daemon-regression-coverage

Conversation

@AmyShang-alt

Copy link
Copy Markdown
Contributor

Summary

Adds daemon-level integration coverage for Vela workspace billing flows and hardens four flaky full-suite regressions.

What changed

  • Adds 30 Vela workspace and billing integration cases across the daemon Vela routes and wallet client.
  • Covers workspace-aware wallet requests, subscription and balance state, team member quota handling, seats and invitations, auto-top-up configuration, and workspace isolation.
  • Fixes the resume-on-failure fake Claude fixture so auth status is not counted as a generation attempt.
  • Extends local timeouts only for three resource-sensitive daemon tests: restart idempotency, screenshot path traversal, and home-tree setup.

Why

Vela API/Web E2E coverage lives in powerformer/vela. These tests protect the Open Design daemon integration boundary so daemon callers continue to interpret Vela workspace and billing behavior correctly.

Validation

  • tests/integrations/vela-wallet.test.ts and tests/integrations/vela.routes.test.ts: 117 passing tests
  • Four repaired regression files: 38 passing tests
  • Daemon TypeScript typecheck
  • pnpm guard
  • git diff --check

@lefarcen

lefarcen commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Closing as superseded by #6348, which landed the production hardening on feat/workspace-team as 722a1c855f83597db604b9a5e98e91e3ef27163f.

#6348 preserves the valid wallet-cache and proxy-boundary fixes from this draft, adds fail-closed protection for Connection-nominated Workspace scope, and includes deterministic red/green coverage. It intentionally excludes this draft's timeout widening and real sleeps.

@lefarcen lefarcen closed this Aug 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants