ci: add code coverage

[lotyp]

Summary by CodeRabbit

• Chores

  • Introduced GitHub Actions workflow for automated unit testing and code coverage reporting.

• New Features

  • Enhanced test commands to always display colored output for better readability.

[vercel]

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

Name	Status	Preview	Comments	Updated (UTC)
laravel-cycle-orm-adapter	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 26, 2024 0:50am

[coderabbitai]

Warning

Rate Limit Exceeded

@lotyp has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 23 minutes and 0 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between 3c054e9 and bb3ab21.

Walkthrough

The recent changes introduce a GitHub Actions workflow for automated unit testing and code coverage reporting in a PHP project. The workflow, defined in testing.yml, sets up the necessary PHP environment, runs tests using Pest, and uploads coverage reports to Codecov. Additionally, the composer.json has been updated to ensure test outputs are always colorized.

Changes

Files	Change Summary
.github/workflows/testing.yml	Introduced a GitHub Actions workflow for unit testing, code coverage, and uploading reports to Codecov.
composer.json	Added the --color=always flag to the test command to ensure colorized output.

In the code where tests now thrive,
Colors bloom, alive they arrive.
With workflows set to run with grace,
Coverage climbs, no bug left to chase.
A rabbit hops, in fields of green,
Celebrating code, so pristine. 🌸🐇

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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.

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 as 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 full the review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

[coderabbitai]

Actionable comments posted: 0

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 7f576d2 and 3c054e9.

Files selected for processing (2)

• .github/workflows/testing.yml (1 hunks)
• composer.json (1 hunks)

Files skipped from review due to trivial changes (1)

• .github/workflows/testing.yml

Additional comments not posted (2)

composer.json (2)

166-166: Good addition of coverage flags to the test command for continuous integration.

---

162-162: Ensure consistency in test command flags across all environments.

Verification successful

---

The composer.json file shows that the --color=always flag is indeed used in the "test" script for the pest command. This confirms that the flag is consistently applied in the test-related command.

Scripts Executed

The following scripts were executed for the analysis:

---

Script:

#!/bin/bash
# Description: Verify that the `--color=always` flag is consistently used in all test-related commands.

# Test: Search for other test commands in the `composer.json` file. Expect: All test commands should use the `--color=always` flag.
rg --type json '"test":' composer.json

Length of output: 58

---

---

Script:

#!/bin/bash
# Description: Extract and display the content of the "test" script from the `composer.json` file.

# Extract the "test" script content.
jq '.scripts.test' composer.json

Length of output: 109

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 75.94%. Comparing base (a2d58b5) to head (bb3ab21).
Report is 17 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##             master     #735   +/-   ##
=========================================
  Coverage     75.94%   75.94%           
  Complexity      252      252           
=========================================
  Files            46       46           
  Lines           927      927           
=========================================
  Hits            704      704           
  Misses          223      223           

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