Skip to content

refactor(expo): rename specs/golden to specs/features - #10225

Closed
mikepitre wants to merge 2 commits into
mike/expo-verify-session-start-on-basefrom
mike/expo-verify-rename-e2e-tests
Closed

mikepitre wants to merge 2 commits into
mike/expo-verify-session-start-on-basefrom
mike/expo-verify-rename-e2e-tests

Conversation

@mikepitre

Copy link
Copy Markdown
Contributor

Description

This is the same change as clerk/clerk-ios#693, for the Expo package in integration/expo-native/. clerk/clerk-android#1090 is the same change for clerk-android. This PR sits on #10221.

Every committed e2e test lives in integration/expo-native/specs/golden/<feature>/, so "golden" had come to mean "committed". The tests are e2e tests, and the folder will hold more of them.

After this PR:

  • integration/expo-native/specs/golden/ is integration/expo-native/specs/features/, the name of the feature map in .claude/skills/verify-clerk-expo/features/. The 13 files moved with no change to their content. specs/explored/, the folder for scratch specs that git ignores, keeps its name.
  • The CLI looks in the new folder. In run --json and in run.json, the kind of a committed spec is committed. It was golden.
  • The skill, integration/expo-native/README.md, one CLI message and three test names say "e2e test". Where a sentence sets a committed test against a scratch spec, it says "committed spec".
  • .github/workflows/verify-e2e.yml changes on one line, the name of the step that runs the tests.

Behavior does not change. run <feature> runs every spec of that feature, and run --all runs every committed spec and no scratch spec. No verb, flag, exit code or rule of discovery changes. No tracked file of this repository holds the word "golden" after this.

The files under integration/expo-native/src/core/ are byte copies of the files of clerk/clerk-ios#693. The changeset is empty, as it is in the other PRs of the stack. No published package changes.

The same tests are found before and after. What run --all, run <feature>, run <feature>/<spec> and run <path> select, and what npx e2e list prints for those files, is 12 spec files, 17 tests on iOS and 15 on Android, on #10221 and on this branch. The two lists differ only in the name of the folder.

npm test in integration/expo-native/ passes 793 of 793, as it does on #10221. npm run typecheck is clean. vitest run --root scripts verify-attach passes 196 of 196.

verify-e2e run 38495475457 on this head ran 17 tests on iOS and 15 on Android, in the 12 files from specs/features/, and all passed. The last run below this change, 38483444520 on #10219, ran the same 32. #10221 is a draft, so its own run skipped the tests, and it changes no file under specs/.

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

🤖 Generated with Claude Code

mikepitre and others added 2 commits October 13, 2026 21:21
Every committed e2e test of `integration/expo-native/` lives in this
folder, so "golden" had come to mean "committed". The folder now has the
name of the skill's feature map.

The CLI finds the tests in the new folder, and the spec kind `golden` is
now `committed`. The kind is in the output of `run --json` and in
`run.json`. No verb, flag, exit code or rule of discovery changes.

The 13 files moved with no change to their content. The changeset is
empty, as it is in the other pull requests of the stack.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The skill, the docs, the workflow, one CLI message and three test names
called the committed e2e tests "golden". They are e2e tests. Where a
sentence sets them against a scratch spec under `specs/explored/`, it
says "committed spec".

The workflow changes on one line, the name of the step that runs the
tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@changeset-bot

changeset-bot Bot commented Oct 14, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 5e12c30

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel

vercel Bot commented Oct 14, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
clerk-js-sandbox Ready Ready Preview Oct 14, 2026 2:04am UTC
swingset Ready Ready Preview Oct 14, 2026 2:04am UTC

Request Review

@coderabbitai

coderabbitai Bot commented Oct 14, 2026

Copy link
Copy Markdown
Contributor

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@mikepitre

Copy link
Copy Markdown
Contributor Author

Replaced by the regrouped stack #10235, #10236, #10237 and #10238, which ends on the same code (tree c2fc7c19). The old stack grew one PR per port from clerk-ios and clerk-android; the new one groups what a reviewer reads together.

@mikepitre mikepitre closed this Oct 14, 2026

This branch was successfully deployed

2 active deployments
Preview – swingset — 5e12c301 Deployed Oct 14, 2026 by vercel[bot]
Preview – clerk-js-sandbox — 5e12c301 Deployed Oct 14, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant