test: fix unit test failures

[vangie]

💻 变更类型 | Change Type

• feat
• fix
• refactor
• perf
• style
• test
• docs
• ci
• chore
• build

🔀 变更说明 | Description of Change

修复单元测试运行报错的问题。

📝 补充信息 | Additional Information

Summary by CodeRabbit

• Tests
  • Enhanced testing configuration to support ECMAScript modules and streamline global variable access.
  • Updated mocked network responses to better simulate production behavior.
  • Refined test execution commands with improved runtime flags.
  • Made minor formatting adjustments for clearer test organization.

[vercel]

@vangie is attempting to deploy a commit to the NextChat Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

This update modifies several test-related configurations and files. The Jest configuration now treats TypeScript files as ECMAScript modules and injects global variables into the testing environment. The test setup adjusts the mocked fetch behavior by changing the JSON response and removing the clone method. Additionally, the test commands in the package configuration have been updated to run Jest via Node with specific experimental flags. A test file has also been updated to include an explicit Jest import and minor formatting improvements.

Changes

File	Change Summary
jest.config.ts	Added properties: extensionsToTreatAsEsm: [".ts", ".tsx"] and injectGlobals: true to enhance Jest configuration.
jest.setup.ts	Modified the mocked fetch: json() now returns an empty array [] instead of {}, and the clone() method has been removed.
package.json	Updated the "test" and "test:ci" scripts to execute Jest via Node with --no-warnings and --experimental-vm-modules flags, using the Yarn binary for Jest.
test/vision-model-checker.test.ts	Added an explicit import of jest from @jest/globals and removed an extraneous empty line for improved code formatting.

Poem

Hi there, I'm Bunny, hopping through the code,
Adjusting tests in every node.
Configs are slick with ESM in the mix,
And mocks are pruned for cleaner tricks.
With Node flags set and tests so fine,
I celebrate these changes – oh, how divine!
🐇💻

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f7cde17 and 0d41a17.

📒 Files selected for processing (4)

• jest.config.ts (1 hunks)
• jest.setup.ts (1 hunks)
• package.json (1 hunks)
• test/vision-model-checker.test.ts (3 hunks)

🔇 Additional comments (9)

test/vision-model-checker.test.ts (2)

1-1: Appropriate Jest import addition.

Adding the explicit import from @jest/globals aligns with the ESM configuration changes in jest.config.ts and helps ensure Jest functions work properly in the new testing setup.

---

54-54: Code formatting improvement.

Removing the empty line improves code consistency.

jest.config.ts (2)

18-18: Essential configuration for TypeScript ESM compatibility.

Setting extensionsToTreatAsEsm properly configures Jest to handle TypeScript files as ECMAScript modules, which is critical for modern TypeScript projects. This addresses potential module-related test failures.

---

19-19: Proper Jest globals configuration.

Setting injectGlobals: true ensures Jest's testing functions are automatically available, which complements the explicit Jest imports in test files. This creates a consistent testing environment.

jest.setup.ts (3)

3-3: Appropriate Jest import addition.

Adding the explicit import from @jest/globals aligns with the ESM configuration and ensures proper access to Jest functions.

---

9-9: Fixed mock response format.

Changing the mock json() method to return an empty array instead of an empty object ensures tests receive the expected data structure, addressing potential test failures where array responses were expected.

---

21-21: Improved type assertion clarity.

The explicit as Response type assertion provides better type safety and clarity in the mock implementation.

package.json (2)

20-20: Critical Jest invocation update.

Running Jest via Node with --experimental-vm-modules enables proper ES modules support, which is essential for the TypeScript ESM configuration. This directly addresses module-related test failures.

---

21-21: Consistent CI test configuration.

Applying the same Node.js flags to the CI test script ensures consistent behavior between local and CI environments, preventing environment-specific test failures.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.