Skip to content

[Tests] Remove filesystem mocks in doc fetch service tests#7908

Draft
gonzaloriestra wants to merge 1 commit into
mainfrom
tests-remove-fs-mock-doc-fetch-1843732053590101784
Draft

[Tests] Remove filesystem mocks in doc fetch service tests#7908
gonzaloriestra wants to merge 1 commit into
mainfrom
tests-remove-fs-mock-doc-fetch-1843732053590101784

Conversation

@gonzaloriestra

Copy link
Copy Markdown
Contributor

Summary

This PR refactors the unit tests for the docFetchService in @shopify/cli to eliminate filesystem mocks, following the testing guidelines for the repository.

Changes

  • Removed vi.mock('@shopify/cli-kit/node/fs') from packages/cli/src/cli/services/commands/doc/fetch.test.ts.
  • Updated the test case that verifies writing to an output path to use inTemporaryDirectory and real filesystem assertions (fileExistsSync, readFile).
  • Ensured compliance with the vitest/prefer-expect-resolves lint rule by using expect().resolves.

How to test your changes?

CI


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

Refactored `packages/cli/src/cli/services/commands/doc/fetch.test.ts` to replace filesystem mocks with real operations using `inTemporaryDirectory`. Verified that `docFetchService` correctly handles directory creation and file writing by asserting the state of the real filesystem.

- Replaced `vi.mock('@shopify/cli-kit/node/fs')` with real fs utilities.
- Updated 'writes the document to the output path instead of stdout' to use `inTemporaryDirectory`.
- Complied with `vitest/prefer-expect-resolves` ESLint rule.
@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 Jun 24, 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