[FIX] run test with coverage command

[PPeitsch]

⚡ Have you read the Contributing Guidelines?

Description

Updated GitHub Actions workflow test command to correctly specify package name for coverage reporting, ensuring accurate Codecov badge and test coverage information.

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would break existing functionality)
• Documentation update
• Performance improvement
• Code style update (formatting, renaming)
• Refactoring (no functional changes)
• CI/CD related changes
• Test coverage improvement
• Other (please describe):

Checklist

• I have followed the project's coding style guidelines
• I have added tests to cover my changes
• All new and existing tests pass locally
• I have updated the documentation accordingly
• I have added type hints where applicable
• I have updated the CHANGELOG.md
• My changes generate no new mypy warnings
• I have checked code formatting with black (line length 100)
• I have run isort for import sorting
• My PR is based on the latest main branch and has no conflicts
• I have added/updated docstrings in NumPy format

[coderabbitai]

Walkthrough

The pull request modifies the GitHub Actions workflow file to adjust the coverage reporting path. The change simplifies the coverage source path by removing the src/ prefix, changing it from src/pkynetics to pkynetics. This modification affects how code coverage is calculated during the testing process, without altering the overall structure of the workflow or its other components.

Changes

File	Change Summary
.github/workflows/test-and-publish.yaml	Updated coverage source path from src/pkynetics to pkynetics

Possibly related PRs

• Fix/coverage #36: Modification of the .github/workflows/test-and-publish.yaml file, with similar GitHub Actions workflow adjustments related to coverage reporting

Poem

🐰 A Rabbit's Coverage Tale 🧪

From src/ to bare path we leap,
Coverage reporting now runs deep
A simple change, yet precise and neat
Our code's embrace becomes more sweet
Hop along, workflow so bright! 🚀

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

✅ All tests successful. No failed tests found.

see 32 files with indirect coverage changes

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

.github/workflows/test-and-publish.yaml (1)

64-64: Consider consolidating test coverage reporting

The workflow currently has two separate test executions:

1. In the test job with coverage
2. In the publish job without coverage

Consider adding coverage reporting to the publish job's test execution as well to maintain consistency and provide coverage data for released versions.

Apply this diff to add coverage reporting to the publish job:

      - name: Test package
-       run: pytest tests/
+       run: |
+         python -m pytest tests/ --cov=pkynetics --cov-report=xml --junitxml=junit.xml

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 090a210 and b8db32b.

📒 Files selected for processing (1)

• .github/workflows/test-and-publish.yaml (1 hunks)