-
Notifications
You must be signed in to change notification settings - Fork 229
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
update pipeline level nf-test documentation #3115
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for nf-core-main-site ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for nf-core-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
sites/docs/src/content/docs/guidelines/pipelines/recommendations/testing.md
Outdated
Show resolved
Hide resolved
|
||
- To ensure all output files are caught, the `params.outdir` should be set the the nf-test variable `outputDir` | ||
- The tag `PIPELINE` and the pipeline name should be added to all tests | ||
- To ensure all output files are caught, it is highly recommended to use the `nft-utils` plugin to parse the output of the pipeline. |
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 provide example code.
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.
that's the example that follows
sites/docs/src/content/docs/guidelines/pipelines/recommendations/testing.md
Outdated
Show resolved
Hide resolved
sites/docs/src/content/docs/guidelines/pipelines/recommendations/testing.md
Outdated
Show resolved
Hide resolved
`stable_path` capture all of the stable files in the output directory, ignoring the files listed in the `.nftignore` file. | ||
|
||
Additional plugins can be used if files with unstable content can be read using a nf-test plugin. | ||
For example for BAM and CRAM files the `nft-bam` plugin is used, while the `nft-vcf` plugin is also used, both in conjonction with `nft-utils`: |
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.
should we move this section into the nf-test assertion examples (and split it up into component tests and pipeline tests?
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.
I like that idea
Co-authored-by: Matthias Hörtenhuber <[email protected]>
@netlify /docs/guidelines/pipelines/recommendations/testing