-
Notifications
You must be signed in to change notification settings - Fork 206
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this 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 🙂
Testing for inputs existing modules such as tools/tests/modules/test_lint.py Line 181 in 52e8109
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!
|
@nf-core-bot update changelog |
@mashehu @mirpedrol I added a |
There was a problem hiding this 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 👍
@nf-core-bot changelog |
merging this now! I hope it's ok 😄 |
Coming from #3530