-
Notifications
You must be signed in to change notification settings - Fork 716
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update hamronization/abricate #4851
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one small question, mainly out of my own curiosity rather than an actual issue
input[1] = '' | ||
input[2] = '' | ||
input[3] = '' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couldn't you use the same inputs as the main test? What you have works, I'm just curious why you chose to have them remain different!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wondered that too.. but then had same thought, 'true not necessarily needed, nm' 😆
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't have a strong opinion about those, but @ahvigil has (see below comment), so I went for same inputs for stub and normal tests now ;)
process { | ||
""" | ||
input[0] = [ [ id:"test" ],file("dummy.tsv") ] | ||
input[1] = '' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think input[1]
should still be one of the valid format strings. If you look at the snapshot for this stub both tsv and json outputs are empty, and the stub will end up doing an echo ... > test.
because the format is an empty string. All of that works in that nothing complains, but doesn't totally test the stub in the way that its meant to be used
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Okay, I changed it to the inputs from the normal test to have it as similar as possible. So far, I used stub tests only for modules with intensive ressource demand (e.g. database downloads or 'out of memory' errors on Github CI checks). But yes, makes sense to keep everything else the same between stub and normal test 👍
echo "hamronize \\ | ||
abricate \\ | ||
${report} \\ | ||
$args \\ | ||
--format ${format} \\ | ||
--analysis_software_version ${software_version} \\ | ||
--reference_database_version ${reference_db_version} \\ | ||
> ${prefix}.${format}" | ||
|
||
touch ${prefix}.${format} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no need to both echo
and touch
here, I think you can pick one
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright, removed!
* abricate --migrate_pytest * Complete nf-test + add stub * Fix linting * Fix linting * Update test names * Update stub test * Stage proper input files for stub tests * Remove `echo <command>` from main.nf
* abricate --migrate_pytest * Complete nf-test + add stub * Fix linting * Fix linting * Update test names * Update stub test * Stage proper input files for stub tests * Remove `echo <command>` from main.nf
PR checklist
versions.yml
file.label
PROFILE=docker pytest --tag <MODULE> --symlink --keep-workflow-wd --git-aware
PROFILE=singularity pytest --tag <MODULE> --symlink --keep-workflow-wd --git-aware
PROFILE=conda pytest --tag <MODULE> --symlink --keep-workflow-wd --git-aware