Remove tags in tests and tag.yml

[chriswyatt1]

PR checklist

Closes #6001

• 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 module conventions in the contribution docs
• If necessary, include test data in your PR.
• Remove all TODO statements.
• Emit the versions.yml file.
• Follow the naming conventions.
• Follow the parameters requirements.
• Follow the input/output options guidelines.
• Add a resource label
• Use BioConda and BioContainers if possible to fulfil software requirements.
• Ensure that the test works with either Docker / Singularity. Conda CI tests can be quite flaky:
  • For modules:
    • nf-core modules test <MODULE> --profile docker
    • nf-core modules test <MODULE> --profile singularity
    • nf-core modules test <MODULE> --profile conda
  • For subworkflows:
    • nf-core subworkflows test <SUBWORKFLOW> --profile docker
    • nf-core subworkflows test <SUBWORKFLOW> --profile singularity
    • nf-core subworkflows test <SUBWORKFLOW> --profile conda

[nvnieuwk]

I think we should keep the tags in the test file. This will make testing in pipelines a lot easier

[chriswyatt1]

Ah ok, yes, if they are needed then we shouldn't default remove them from all the modules

[edmundmiller]

I think we should revisit the tags in the modules. With the new "only test what's changed" and dependencies in nf-test I'm not sure the amount of tags is necessary.

Not sure what to do differently but it's just overkill.

Think that's outside the scope of this PR I think removes the yamls is safe.

[nvnieuwk]

Yeah that's mostly fine in modules but it does help in pipelines where you want to test a specific part of your pipeline. The tags are mostly automated by tools anyway so it's no extra work for developers.

[jfy133]

I feel the tags are still useful for doing one off tests while developping, but the modules and modules_nf-core oones are not that useful.

So I vote to remove those two and keep just the ones that are specific to that module (e.g. that module, and any upstream modules used during teh testing)

[jfy133]

I think we should revisit the tags in the modules. With the new "only test what's changed" and dependencies in nf-test I'm not sure the amount of tags is necessary.

The only test what's changed is fine for just testing on GHA (I would presume?) Not locally, or?

[maxulysse]

I think it's overkill to have tags too, so for all removal

[jfy133]

wait I'm confused, is the purpose of this to have literally 0 tags at all?

[mirpedrol]

Hi! We have some issues in tools to update the pipeline template so that we don't need tags in modules, see nf-core/tools#2855 and nf-core/tools#2854.
So it looks OK to remove them.

To test only one module, you can use the path, so there's no need to use a tag.