Skip to content

ci: run shared tests standalone - #76

Merged
buzz-code merged 2 commits into
mainfrom
claude/standalone-ci
Nov 4, 2026
Merged

buzz-code merged 2 commits into
mainfrom
claude/standalone-ci

Conversation

@buzz-code

Copy link
Copy Markdown
Owner

What

  • Add package.json (private, nra-client-shared) with yarn test = jest; Jest and Babel config is inline (jsdom, @shared/* mapped to repo root, babel-jest with env/react/typescript presets, jest-dom and whatwg-fetch setup).
  • Add yarn.lock (seeded from react-admin-nestjs client/yarn.lock, pruned), .gitignore, and .github/workflows/test.yml (PR + push to main, Node 20, yarn install --frozen-lockfile, yarn test).
  • Add standalone-run note to the Tests section of AGENTS.md.

No component code or exports changed.

Why

Tests only ran from a consumer's client/shared with the consumer's Jest/Babel config. They now run in this repo's own CI with no consumer host.

Result

Local: 38 suites passed, 1 skipped (utils/testing/entities.test.js, a describe.skip pre-existing helper); 221 tests passed, 1 skipped.

Consumer safety

Config lives in package.json only: no babel.config.js, .babelrc or jest.config.js. Consumer Jest reads only its own root config, and the package name is unique, so no haste collision. No node_modules exist in the submodule checkout.

Drift risk

Dependency versions are duplicated from the consumers' client/package.json. Keep them in sync when consumers bump react-admin, React, Jest or testing-library.

Tracking

No ops issue: buzz-code/ops was inaccessible from this session.


Generated by Claude Code

Add package.json (private nra-client-shared, inline Jest/Babel config), yarn.lock and a GitHub Actions workflow so the shared tests run without a consumer host.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YcJKachbaAqM1u1cHJDwMf
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01YcJKachbaAqM1u1cHJDwMf
@buzz-code
buzz-code merged commit 510cf19 into main Nov 4, 2026
1 check passed
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