-
Notifications
You must be signed in to change notification settings - Fork 206
template - basic pipeline level nf-test tests #3469
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
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.
we should not merge this without a corresponding PR with docs
That's on the way |
Thinking that people might not want to use nf-test, so we should have a flag for this. |
Co-authored-by: Matthias Hörtenhuber <mashehu@users.noreply.github.com>
@@ -401,7 +403,9 @@ test_config: | |||
- "conf/test_full.config" | |||
- ".github/workflows/awsfulltest.yml" | |||
- ".github/workflows/awstest.yml" | |||
- ".github/workflows/ci.yml" | |||
- ".github/workflows/nf-test.yml" |
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.
when skipping tests, we should also skip nf-test.config
and the tests
directory
@@ -416,7 +420,9 @@ test_config: | |||
files_exist: | |||
- "conf/test.config" | |||
- "conf/test_full.config" | |||
- ".github/workflows/ci.yml" | |||
- ".github/workflows/nf-test.yml" |
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.
skip nf-test files
.github/workflows/ci.yml | ||
.github/workflows/nf-test.yml | ||
.github/actions/get-shards/action.yml | ||
.github/actions/nf-test/action.yml |
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.
We should also lint for nf-test files
I would say if we move to nf-test that should be the only way to test. There could be an option to skip testing, but if you test, it has to be with nf-test |
💯 i guess the difference to before is now that nf-test adds some files to the template and given some people want a very bare-bone structure, we should probably have a skip feature. |
Needs some more improvments, I'm trying it out in nf-core/rnavar#178, which uncovers some issue I didn't find in sarek. |
Co-authored-by: Júlia Mir Pedrol <mirp.julia@gmail.com>
|
shard: ${{ fromJson(needs.nf-test-changes.outputs.shard) }} | ||
profile: [conda, docker, singularity] | ||
isMain: | ||
- ${{ github.base_ref == 'master' || github.base_ref == 'main' }} |
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.
we can think of updating this test when we fully remove master
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.
only one last comment, otherwise LGTM 🚀
Co-authored-by: Matthias Hörtenhuber <mashehu@users.noreply.github.com>
I can take care of fixing the failing test and then merging 👍 |
add a feature to skip nf-test for custom pipelines
Codecov ReportAttention: Patch coverage is
☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Related updated docs: nf-core/website#3216
PR checklist
CHANGELOG.md
is updateddocs
is updated