Skip to content

[Tests] Remove filesystem mocks in execute-bulk-operation.test.ts#7543

Open
gonzaloriestra wants to merge 1 commit into
mainfrom
remove-fs-mocks-execute-bulk-op-4480568056550116275
Open

[Tests] Remove filesystem mocks in execute-bulk-operation.test.ts#7543
gonzaloriestra wants to merge 1 commit into
mainfrom
remove-fs-mocks-execute-bulk-op-4480568056550116275

Conversation

@gonzaloriestra
Copy link
Copy Markdown
Contributor

@gonzaloriestra gonzaloriestra commented May 14, 2026

Why

The test suite for executeBulkOperation was using global filesystem mocks, which are fragile and can lead to non-deterministic tests or hide actual bugs in filesystem interactions.

What

  • Removed vi.mock('@shopify/cli-kit/node/fs') from packages/app/src/cli/services/bulk-operations/execute-bulk-operation.test.ts.
  • Refactored tests that write files to use inTemporaryDirectory and joinPath.
  • Replaced mock call assertions (toHaveBeenCalledWith) with actual state verification (readFile and content comparison).
  • Added missing version parameter to runBulkOperationMutation call in one test to match service expectations and fix a failing assertion caused by removing the mock.

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

Replace global filesystem mocks with real filesystem operations within
temporary directories. This improves test reliability by verifying actual
file content on disk instead of merely asserting mock call counts.

- Removed `vi.mock('@shopify/cli-kit/node/fs')`
- Updated tests to use `inTemporaryDirectory`
- Replaced `toHaveBeenCalledWith` on `writeFile` with `readFile` content checks
- Fixed a test expectation by adding missing `version` parameter to `runBulkOperationMutation`
@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 14, 2026
@gonzaloriestra gonzaloriestra added the Jules Created by Jules label May 14, 2026
@gonzaloriestra gonzaloriestra marked this pull request as ready for review May 14, 2026 13:24
@gonzaloriestra gonzaloriestra requested a review from a team as a code owner May 14, 2026 13:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Jules Created by Jules 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