Skip to content

[Tests] Refactor doc fetch service tests to remove fs mocks#8015

Draft
gonzaloriestra wants to merge 1 commit into
mainfrom
tests-refactor-fetch-doc-fs-mocks-10656394579371662531
Draft

[Tests] Refactor doc fetch service tests to remove fs mocks#8015
gonzaloriestra wants to merge 1 commit into
mainfrom
tests-refactor-fetch-doc-fs-mocks-10656394579371662531

Conversation

@gonzaloriestra

Copy link
Copy Markdown
Contributor

Followed the instructions in .agents/automated-tasks/tests.md to replace filesystem mocks with real operations in a temporary directory for docFetchService tests in packages/cli/src/cli/services/commands/doc/fetch.test.ts.

Changes:

  • Removed filesystem mocking in packages/cli/src/cli/services/commands/doc/fetch.test.ts.
  • Updated writes the document to the output path instead of stdout test case to use inTemporaryDirectory and joinPath.
  • Verified file existence and content using fileExists and readFile.
  • Ensured all asynchronous assertions use .resolves to satisfy linting requirements.
  • Confirmed all tests pass, and linting/type-checking are successful.

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

- Remove `vi.mock('@shopify/cli-kit/node/fs')` from `packages/cli/src/cli/services/commands/doc/fetch.test.ts`.
- Use `inTemporaryDirectory` to create a real temporary directory for testing file output.
- Use `await expect(...).resolves` for asynchronous assertions to comply with ESLint rules.
- Verify file creation and content using `fileExists` and `readFile`.
@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 Jul 7, 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