Update workflows for parallel tests

[notAreYouScared]

[coderabbitai[bot]]

[!WARNING]

Rate limit exceeded

@notAreYouScared has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 7 minutes and 19 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

Reviewing files that changed from the base of the PR and between 47189c08a9fbcfe783b5d7216b1577ba66dc925f and b9d11e2a1be2dbceec628ee707b47b1837786841.

📒 Files selected for processing (1)

• .github/workflows/ci.yaml (6 hunks)

📝 Walkthrough

Walkthrough

CI workflow adds a migration step and switches test execution to Composer's parallel runner; composer.json gains a ParaTest dev dependency and scripts test and test:parallel.

Changes

Cohort / File(s)	Summary
CI Workflow .github/workflows/ci.yaml	Adds a new step that runs migrations (php artisan migrate --force) before tests; replaces direct Pest invocations with Composer parallel runner calls: composer run test:parallel -- tests/Unit and composer run test:parallel -- tests/Integration across SQLite, MySQL, MariaDB, and PostgreSQL job matrices.
Composer configuration composer.json	Adds brianium/paratest to require-dev and adds scripts test (php artisan test) and test:parallel (php artisan test --parallel).

Sequence Diagram(s)

sequenceDiagram
  autonumber
  participant CI as CI job
  participant Composer as Composer scripts
  participant Artisan as php artisan
  participant ParaTest as ParaTest / php artisan test --parallel
  participant Tests as Test suite (Unit/Integration)

  CI->>Artisan: run `php artisan migrate --force`
  Artisan-->>CI: migration success/failure
  CI->>Composer: run "composer run test:parallel -- tests/Unit" or "tests/Integration"
  Composer->>ParaTest: invokes `php artisan test --parallel` (via script)
  ParaTest->>Tests: distribute and run tests in parallel
  Tests-->>ParaTest: results
  ParaTest-->>Composer: aggregated results/exit code
  Composer-->>CI: exit code / logs

Pre-merge checks

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No description was provided by the author, making it impossible to assess if it relates to the changeset.	Add a pull request description explaining the motivation, changes, and benefits of implementing parallel test execution.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating CI workflows to use parallel test execution via paratest and new composer scripts.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}