Skip to content

[Tests] Remove filesystem mocks in extension.test.ts#7681

Draft
gonzaloriestra wants to merge 1 commit into
mainfrom
tests-remove-fs-mocks-extension-build-2100486209806891838
Draft

[Tests] Remove filesystem mocks in extension.test.ts#7681
gonzaloriestra wants to merge 1 commit into
mainfrom
tests-remove-fs-mocks-extension-build-2100486209806891838

Conversation

@gonzaloriestra
Copy link
Copy Markdown
Contributor

WHY are these changes introduced?

Following the testing standards to avoid mocking the filesystem and use real temporary directories instead. This makes tests more robust and less coupled to implementation details.

WHAT is this pull request doing?

Refactors packages/app/src/cli/services/build/extension.test.ts to remove vi.mock('@shopify/cli-kit/node/fs'). It now uses inTemporaryDirectory and real filesystem operations for setup and assertions.

How to test your changes?

CI

Post-release steps

None

Checklist

  • I've considered possible cross-platform impacts (Mac, Linux, Windows)
  • I've considered possible documentation changes
  • I've considered analytics changes to measure impact
  • The change is user-facing — I've identified the correct bump type (patch for bug fixes · minor for new features · major for breaking changes) and added a changeset with pnpm changeset add

PR created automatically by Jules for task 2100486209806891838 started by @gonzaloriestra

This PR refactors the unit tests for `buildFunctionExtension` in `packages/app/src/cli/services/build/extension.test.ts` to eliminate filesystem mocks. Following our updated testing standards, it now uses real temporary directories and filesystem operations via `@shopify/cli-kit/node/fs` utilities.

Changes:
- Removed global `vi.mock('@shopify/cli-kit/node/fs')`.
- Wrapped tests in `inTemporaryDirectory`.
- Updated test setup to create real files and directories.
- Refined assertions to verify actual state on disk where appropriate.
- Ensured proper type-safety for mocks by casting to `Writable` or `any` where needed.
- Fixed mock rejection to use `Error` objects instead of strings.
@google-labs-jules
Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@github-actions github-actions Bot added the no-changelog This PR doesn't include a changeset entry. Is an internal only change not relevant to end users. label May 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-changelog This PR doesn't include a changeset entry. Is an internal only change not relevant to end users.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant