fix: initialize sourcePatterns in tester context to prevent undefined error#10020
Merged
Conversation
GiladShoham
approved these changes
Oct 1, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the issue where Jest tester with
useSourceFiles: truecrashes withCannot read properties of undefined (reading 'toArray')duringbit test.Problem
When Jest tester is configured with
useSourceFiles: true, it expectscontext.sourcePatternsto be available. However, duringbit test, the tester context only includedpatternsbut notsourcePatterns, causing an undefined error. ThesourcePatternswas only being populated duringbit buildtask by the tester-task component.Solution
Initialize
sourcePatternsin the tester service to default to the same value aspatterns. This ensures:bit test:sourcePatternsequalspatterns, allowing jest-tester to work correctly with source filesbit build: The jest-tester-task can still overridesourcePatternswith capsule-specific paths