Improved nf test scope docs to describe how portable nf-core/modules 'tests' should be

[jfy133]

As discussed here: https://nfcore.slack.com/archives/C049MBCEW06/p1731521149600189

@netlify /docs/guidelines/components/modules

[netlify]

✅ Deploy Preview for nf-core-main-site ready!

Name	Link
🔨 Latest commit	8abc713
🔍 Latest deploy log	https://app.netlify.com/sites/nf-core-main-site/deploys/675028bf80a05e0008f4e38c
😎 Deploy Preview	https://deploy-preview-2876--nf-core-main-site.netlify.app/docs/guidelines/components/modules
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for nf-core-docs ready!

Name	Link
🔨 Latest commit	8abc713
🔍 Latest deploy log	https://app.netlify.com/sites/nf-core-docs/deploys/675028bf0934be00084637fe
😎 Deploy Preview	https://deploy-preview-2876--nf-core-docs.netlify.app/docs/guidelines/components/modules
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[jfy133]

@christopher-hakkaart as always language clean up would be grand if you have a moment <3

[mashehu]

and version snapshot

[mirpedrol]

👍

[MatthiasZepper]

In that discussion, there was a quite neat proposal: Using dedicated tags to distinguish the two: tag "tethered" and tag "portable" for example. (alternatively also tag "rooted" and tag "detached").

In that case, nf-core modules install could just skip the tests tagged as tethered, respectively rooted.

Otherwise, tests from the modules' repo would need to be manually deleted in the pipeline repositories after every run of nf-core modules update.

[christopher-hakkaart]

No major objections.

Comments are suggestions that I think help improve clarity but feel free to disagree.

[mirpedrol]

Otherwise, tests from the modules' repo would need to be manually deleted in the pipeline repositories after every run of nf-core modules update.

You can use nf-core modules patch when removing the tests. However, this wouldn't be my preferred solution either. I think modules and subowrkflows tests should be run on the modules repo, we don't need to rerun them with pipeline tests.