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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regex wildcard in testPathIgnorePatterns may over-exclude tests
Medium Severity
testPathIgnorePatternsvalues are treated as regex patterns matched against absolute file paths, not as file system paths. The.in./src/and./tests/integration/is a regex wildcard (matching any character), not a literal dot meaning "current directory." While<rootDir>was a special Jest token that got replaced with the actual project root path (yielding a precise pattern like/home/user/sentry-cli/src/),./src/is a loose regex matching any path containing<any-char>/src/. If the project lives under a path containing/src/(e.g.,/home/dev/src/sentry-cli/), this pattern would match and exclude all test files. The PR description indicates onlysetupFileshad the<rootDir>resolution issue —testPathIgnorePatternsmay not have needed changing.