Add nftests custom modules

[nschcolnicov]

PR checklist

Closes #XXX

• 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

[famosab]

You will also need to remove the modules from the pytest config file. Afterwards we should be good to go :)

https://github.com/nf-core/modules/blob/816ff3b787af7e12e75a7d95f76b631f474853ee/tests/config/pytest_modules.yml#L112C1-L120C53

[nschcolnicov]

There is a linting error:

But running the command suggested nf-core modules lint --fix reveals that the changes that it is expecting are not correct, it tries to convert all of the output channels into map type:

What do you think about this? @famosab

[famosab]

Huh that is interesting can you commit the "fixed" yaml files and push them to this PR so I can have a look?

[nschcolnicov]

Huh that is interesting can you commit the "fixed" yaml files and push them to this PR so I can have a look?

Take a look: eb84fde

[famosab]

I think the update was needed because we changed one of the outputs per my request. But why --fix now does these kind of replacements also seems off to me. @mashehu @mirpedrol what do you guys think? is that expected behavior and should we just manually revert these changes or is something wrong with tools?

[mirpedrol]

Changing the name of the output and using *R_sessionInfo.log is the right change but replacing the type and description is not! We saw the same with other modules, it must be a weird bug with the --fix command, you can revert this.
And the same for the other outputs where this happened, like filtered.csv and tests.csv

[famosab]

We are almost done :)

[famosab]

there was a new convention recently, maybe you can update to adhere to that: https://nf-co.re/docs/guidelines/components/modules#configuration-of-extargs-in-tests

[nschcolnicov]

Just to make sure, you are requesting me to pass the values that I'm providing via ext.args using params instead of the actual value? Didn't you correct me to do it this way on a previous comment? https://github.com/nf-core/modules/pull/7201/files/816ff3b787af7e12e75a7d95f76b631f474853ee#r1888548704 Want to make sure I'm doing it the exact way you are suggesting

[famosab]

If I did then I am sorry. But what is meant is that the params that you need to pass are written directly in the nf.test file which makes its directly understandable for other people that look at your tests and then they do not have to go through multiple nextflow.config files.

[nschcolnicov]

No, sorry, you are right, I was wrong both times, I just wasn't understanding how you wanted me to structure the config, I think I have now understood and addressed the issues, let me know what you think @famosab 😄

[famosab]

see comment above

[nschcolnicov]

It seems that I'm no longer able to push to this branch:

@famosab @mirpedrol Do you know what could be wrong?

[famosab]

@nschcolnicov I think you should be able to push again :)