Update nf-test snapshot

[BenjaminWehnert1008]

PR checklist

• This comment contains a description of changes (with reason).
• If you've fixed a bug or added code that should be tested, add tests!
• If you've added a new tool - have you followed the pipeline conventions in the contribution docs
• If necessary, also make a PR on the nf-core/deepmutscan branch on the nf-core/test-datasets repository.
• Make sure your code lints (nf-core pipelines lint).
• Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
• Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
• Usage Documentation in docs/usage.md is updated.
• Output Documentation in docs/output.md is updated.
• CHANGELOG.md is updated.
• README.md is updated (including new tool citations and authors/contributors).

[BenjaminWehnert1008]

@mashehu I've updated the test snapshot, but nf-test still fails, do you have an idea why and also how to proceed? Thanks!

[mashehu]

looks like the test produces more files in the CI then you currently have. How did you update your snapshots?

[BenjaminWehnert1008]

looks like the test produces more files in the CI then you currently have. How did you update your snapshots?

nf-test test tests/default.nf.test --profile docker --update-snapshot

[mashehu]

Can you try it with nf-test test tests/default.nf.test --profile +docker --update-snapshot otherwise the test profile might be overwritten https://www.nf-test.com/docs/configuration/#managing-profiles

[BenjaminWehnert1008]

@mashehu, it seems to not fully resolve it...

[mashehu]

I excluded a bit more unstable R files from the snapshot (should just check names for them). Can you try to recreate the snapshot on your side again @BenjaminWehnert1008 ?