test: add more tests

[fengmk2]

Summary by CodeRabbit

• New Features

  • Enhanced test command to support running tests from multiple files simultaneously
  • Added example demonstrating how to specify multiple test files in a single command

• Documentation

  • Updated command examples to clarify usage of test and coverage commands with multiple files

• Tests

  • Added new test case to validate running tests with multiple file inputs

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
egg-bin	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 3, 2025 0:32am

[coderabbitai]

Walkthrough

The pull request introduces enhanced documentation for the cov and test commands by adding examples that demonstrate running tests with multiple test files in a single command. This change provides users with clearer guidance on executing tests across different files. The test suite for the test command has also been updated with a new test case to validate the multi-file test execution functionality.

Changes

File	Change Summary
src/commands/cov.ts	Added example showing multiple test files in coverage command
src/commands/test.ts	Added example for running tests from multiple files
test/commands/test.test.ts	Added new test case for multi-file test execution, removed .debug() method calls

Sequence Diagram

sequenceDiagram
    participant User
    participant TestRunner
    participant TestFiles
    User->>TestRunner: Run tests with multiple files
    TestRunner->>TestFiles: Execute test1.ts
    TestRunner->>TestFiles: Execute test2.ts
    TestRunner-->>User: Display test results

Loading

Possibly related PRs

• fix: auto import tsconfig-paths/register.js #282: Modifications to test/commands/test.test.ts file, focusing on test suite enhancements

Poem

🐰 Hop, hop, testing we go!
Multiple files in a single throw
Comma-separated magic spell
Tests running, all is well
Coverage spreads its wings so bright 🧪

---

📜 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 e91ccbe and f97a9a4.

📒 Files selected for processing (3)

• src/commands/cov.ts (1 hunks)
• src/commands/test.ts (1 hunks)
• test/commands/test.test.ts (3 hunks)

🔇 Additional comments (6)

src/commands/cov.ts (1)

16-16: Great addition to the examples!
Adding a multi-file example enhances user understanding of coverage usage for multiple tests in a single command.

src/commands/test.ts (1)

25-25: Good clarity for multi-file test usage.
Providing an example that shows how to specify multiple files in one command is helpful for users.

test/commands/test.test.ts (4)

14-14: No concerns with commenting out debug calls.
Commenting out .debug() lines helps maintain cleaner test output.

---

23-38: Well-structured test for multiple file inputs.
This new test block effectively verifies the multi-file test execution capability. The separate checks for distinct test file outputs and passing counts improve coverage and confidence.

---

45-45: Consistent debug removal.
Again, removing .debug() lines reduces noise in the test output.

---

57-57: Consistent debug removal.
No issue removing the debug statement here for cleaner test logs.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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. (Beta)
• @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.

[pkg-pr-new]

Open in Stackblitz

npm i https://pkg.pr.new/eggjs/bin/@eggjs/bin@283

commit: f97a9a4

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.79%. Comparing base (515614a) to head (f97a9a4).
Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #283   +/-   ##
=======================================
  Coverage   95.78%   95.79%           
=======================================
  Files          22       22           
  Lines        1068     1070    +2     
  Branches      177      177           
=======================================
+ Hits         1023     1025    +2     
  Misses         45       45           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.