# \#nf-test

**URL:** https://community.seqera.io/tag/nf-test/44.md

[Latest](https://community.seqera.io/latest.md) · [Categories](https://community.seqera.io/categories.md) · [Tags](https://community.seqera.io/tags.md)

---

## [Relative paths in nf-test](https://community.seqera.io/t/relative-paths-in-nf-test/2261)

<div class="topic-metadata">

**Author:** [@bskubi](https://community.seqera.io/u/bskubi)\
**Replies:** 1\
**Last updated:** [July 11, 2025, 10:51am UTC](https://community.seqera.io/t/relative-paths-in-nf-test/2261 "2025-07-11T10:51:37Z")

</div>

My pipeline uses a sample file that stores relative paths to resource files. Running the pipeline with nextflow itself works fine, but with nf-test, it can’t find the resource files. I have tried a few things that did no…

---

## [StackOverflowError when chaining modules for nf-test](https://community.seqera.io/t/stackoverflowerror-when-chaining-modules-for-nf-test/2211)

<div class="topic-metadata">

**Author:** [@mcmero](https://community.seqera.io/u/mcmero)\
**Replies:** 2\
**Last updated:** [June 24, 2025, 2:45am UTC](https://community.seqera.io/t/stackoverflowerror-when-chaining-modules-for-nf-test/2211 "2025-06-24T02:45:00Z")

</div>

I’m submitting a module for nf-core (see PR). My nf-test takes the output file from my first module preparesegmentation and uses it as input for my second module runsegmentationontile. I have checked the nf-test docs on …

---

## [Nf-test: Capture all process/workflow outputs without capturing md5sums of files in snapshots](https://community.seqera.io/t/nf-test-capture-all-process-workflow-outputs-without-capturing-md5sums-of-files-in-snapshots/611)

<div class="topic-metadata">

**Author:** [@nvnieuwk](https://community.seqera.io/u/nvnieuwk)\
**Replies:** 0\
**Last updated:** [March 28, 2024, 3:46pm UTC](https://community.seqera.io/t/nf-test-capture-all-process-workflow-outputs-without-capturing-md5sums-of-files-in-snapshots/611 "2024-03-28T15:46:38Z")

</div>

nf-test snapshots automatically create md5sums of files when they get an absolute path to a file. This can cause some issues when the output files are not 100% stable between reruns (e.g. when the date is included somewh…

---

## [Nf-test: Get the relative paths of all files in a pipeline output folder](https://community.seqera.io/t/nf-test-get-the-relative-paths-of-all-files-in-a-pipeline-output-folder/609)

<div class="topic-metadata">

**Author:** [@nvnieuwk](https://community.seqera.io/u/nvnieuwk)\
**Replies:** 0\
**Last updated:** [March 28, 2024, 12:41pm UTC](https://community.seqera.io/t/nf-test-get-the-relative-paths-of-all-files-in-a-pipeline-output-folder/609 "2024-03-28T12:41:41Z")

</div>

Sometimes the pipeline outputs are not stable and thus snapshot(path("${outputDir}").list()) will not be enough since the md5sums created will be different. This snippet shows an alternative way to check if all files in …