+
Skip to content

Linting: Addressing more cases than can happen when processing input and output values #3541

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 9 commits into from
May 8, 2025

Conversation

toniher
Copy link
Member

@toniher toniher commented Apr 23, 2025

Coming from #3530

Copy link

codecov bot commented Apr 23, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 76.36%. Comparing base (742897d) to head (622ace0).
Report is 31 commits behind head on dev.

☔ 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.

@toniher toniher requested a review from mirpedrol April 23, 2025 14:45
Copy link
Contributor

@mashehu mashehu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please add test cases for this changes, so we don't run into this again 🙂

@toniher
Copy link
Member Author

toniher commented Apr 24, 2025

please add test cases for this changes, so we don't run into this again 🙂

@mashehu

Testing for inputs existing modules such as trinity https://github.com/nf-core/modules/blob/d802effd844103fcc5e233184f95c84026ed44d6/modules/nf-core/trinity/main.nf#L12 and for output ones such as trimgalore https://github.com/nf-core/modules/blob/d802effd844103fcc5e233184f95c84026ed44d6/modules/nf-core/trimgalore/main.nf#L14 I think could be enough. Actually, thanks to the trimgalore already present

def test_modules_lint_trimgalore(self):
I noticed that something was wrong. Can you point me if simply adding in test/modules/test_lint.py a function for trinity could be enough for triggering the test? Should anything else be added as well somewhere else? (This is my first time adding a nf-core tool test). Thx!

@toniher
Copy link
Member Author

toniher commented May 5, 2025

@nf-core-bot update changelog

@toniher
Copy link
Member Author

toniher commented May 5, 2025

@mashehu @mirpedrol I added a trinity module test for linting. I suspect it went through, but I am not fully sure from Github actions outcomes. Let me know!

@toniher toniher requested a review from mashehu May 5, 2025 16:21
Copy link
Member

@mirpedrol mirpedrol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @toniher, sorry for the late reply. The test you added looks good 🙂 I think it is ready to merge 👍

@mirpedrol mirpedrol changed the title Addressing more cases than can happen when processing input and output values Linting: Addressing more cases than can happen when processing input and output values May 7, 2025
@mirpedrol
Copy link
Member

@nf-core-bot changelog

@mirpedrol
Copy link
Member

merging this now! I hope it's ok 😄

@mirpedrol mirpedrol merged commit e5ec63b into nf-core:dev May 8, 2025
97 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants
点击 这是indexloc提供的php浏览器服务,不要输入任何密码和下载