Add test environment to readme

[jan-janssen]

Summary by CodeRabbit

• Documentation
  • Added a "Test Environment" entry with a link to the relevant section in the developer documentation within the "Support & Contribution" section of the README.

[coderabbitai]

Walkthrough

A new "Test Environment" entry was added to the "Support & Contribution" section of the README documentation index, linking to the relevant developer documentation section. No other modifications were made to the README content or to any code or public entity declarations.

Changes

File	Change Summary
README.md	Added a "Test Environment" entry under "Support & Contribution" with a link to developer docs

Poem

In README fields, a new link grows,
"Test Environment" now clearly shows.
For contributors seeking where to test,
This path will guide them to the best.
🐇 Documentation blooms anew—
With every change, we hop right through!

---

📜 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 4084bf0 and cbf6adf.

📒 Files selected for processing (1)

• README.md (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (17)

• GitHub Check: notebooks_integration
• GitHub Check: unittest_mpich (macos-latest, 3.13)
• GitHub Check: unittest_mpich (ubuntu-latest, 3.12)
• GitHub Check: unittest_mpich (ubuntu-latest, 3.11)
• GitHub Check: unittest_flux_mpich
• GitHub Check: unittest_mpich (ubuntu-latest, 3.13)
• GitHub Check: unittest_openmpi (ubuntu-latest, 3.11)
• GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-openmpi.yml)
• GitHub Check: unittest_openmpi (ubuntu-latest, 3.13)
• GitHub Check: unittest_openmpi (macos-latest, 3.13)
• GitHub Check: benchmark (ubuntu-latest, 3.13, .ci_support/environment-mpich.yml)
• GitHub Check: unittest_old
• GitHub Check: notebooks
• GitHub Check: unittest_openmpi (ubuntu-latest, 3.12)
• GitHub Check: unittest_win
• GitHub Check: unittest_flux_openmpi
• GitHub Check: minimal

🔇 Additional comments (1)

README.md (1)

160-160: New “Test Environment” entry added correctly.
The indentation and link syntax match the surrounding items. Please verify that the #test-environment anchor exists in the 4-developer.html page to prevent a broken link.

---

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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in 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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.81%. Comparing base (4084bf0) to head (28d6ac0).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #649   +/-   ##
=======================================
  Coverage   96.81%   96.81%           
=======================================
  Files          29       29           
  Lines        1288     1288           
=======================================
  Hits         1247     1247           
  Misses         41       41           

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.