You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @lukfor ! Thank you very much for getting the recent release out so quickly 🙏🏽 ! We have managed to simplify a lot of the nf-test code by implementing the functionality provided in #184
We are now finishing up with the CI and realised that we need 1 (famous last words!) more feature to help us run targeted tests in our CI/CD.
Following on from #187 would it be possible to have another option in nf-test list that returns the name of the --target component that is being tested, please?
Ideally, we would also have the ability to select which component this returns. For example:
nf-test list --silent --format csv --target process <TEST_PATH>
nf-test list --silent --format csv --target workflow <TEST_PATH>
nf-test list --silent --format csv --target function EST_PATH>
The --target option could also be decoupled from the type of component being returned if that makes more sense on the implementation side.
At the moment, we are trying to use hacky bash to restrict the tags for testing but that's not a flexible solution....
Let us know what you think!!! This is literally the last thing (famous last words!!) we need for our standardised V2 nf-test release of nf-core/fetchngs
The text was updated successfully, but these errors were encountered:
For what it's worth, I think we should have two args for nf-test list here:
--target
Returns the function/process/workflow name
This one could replace --tags as a new arg --output names/targets/tags to make it more generic.
--filter
Return only results relating to a function/process/workflow/pipeline
The second one could be used with nf-test test for some additional filtering. e.g. nf-test test --filter workflows will only test workflow level tests.
Hi @lukfor ! Thank you very much for getting the recent release out so quickly 🙏🏽 ! We have managed to simplify a lot of the nf-test code by implementing the functionality provided in #184
We are now finishing up with the CI and realised that we need 1 (famous last words!) more feature to help us run targeted tests in our CI/CD.
Following on from #187 would it be possible to have another option in
nf-test list
that returns the name of the--target
component that is being tested, please?For example, this would return:
SRATOOLS_FASTERQDUMP
for thisprocess
testFASTQ_DOWNLOAD_PREFETCH_FASTERQDUMP_SRATOOLS
for thisworkflow
testisSraId
for thisfunction
testIdeally, we would also have the ability to select which component this returns. For example:
The
--target
option could also be decoupled from the type of component being returned if that makes more sense on the implementation side.At the moment, we are trying to use hacky bash to restrict the tags for testing but that's not a flexible solution....
Let us know what you think!!! This is literally the last thing (famous last words!!) we need for our standardised V2 nf-test release of nf-core/fetchngs
The text was updated successfully, but these errors were encountered: