Skip to content

Cascade-update test infrastructure for rebrand #216

@alexey-pelykh

Description

@alexey-pelykh

Summary

After #214 renames infrastructure files (tmp-openclaw-dir.tstmp-remoteclaw-dir.ts, openclaw-root.tsremoteclaw-root.ts) and updates production constants (HTTP headers, temp dir prefixes), ~580 test files have stale references that need cascade-updating.

What needs to change

1. Import path updates (~70 files)

All test files importing from the old infrastructure filenames:

  • tmp-openclaw-dir.jstmp-remoteclaw-dir.js
  • openclaw-root.jsremoteclaw-root.js

2. Temp directory prefixes (~500+ files)

Test setup code creates temp directories with openclaw prefixes:

  • mkdtemp("openclaw-test-home-")mkdtemp("remoteclaw-test-home-")
  • mkdtemp("openclaw-media-test-")mkdtemp("remoteclaw-media-test-")
  • And similar patterns across src/ and test/ directories

3. HTTP header assertions (~10 files)

Test assertions checking protocol headers:

  • x-openclaw-session-keyx-remoteclaw-session-key

4. Fixture data and assertions (~50+ files)

  • Fixture strings, mock data, and test assertions referencing "openclaw"
  • Test helper imports and paths

Acceptance Criteria

  • All import paths referencing renamed files updated
  • All temp dir prefixes updated from openclaw to remoteclaw
  • All HTTP header assertions updated
  • All fixture data and assertions updated
  • pnpm build passes
  • pnpm test passes

Blocked by

Blocked by: #214 (file renames must land first)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions