There are only really three ways to get around thi...
# nf-test
a
There are only really three ways to get around this that I can think of off the top of my head and they may not actually work: • execute the tests from a different directory (you'd need to also have a
.nf-test.config
there though I think) • Try and leverage
options
and use
-C some-config
to overwrite any locally applied config (no idea if this would actually succeed) • Move all your
modules.config
into a profile and don't use that profile when running the local module tests. (Users would then need to use this profile to properly run the pipeline which would probably be a bit annoying)
👍 1