Develop full suite of tests for manual execution

[jfy133]

Description of feature

A major problem we currently have during development is our CI tests are nowhere near comprehensive enough due to the pipeline utilising extremely large database files that do not fit in GHA resource allocations.

We should develop and document a suite of manual tests developers should run on their own infrastructure to ensure the pipeline is indeed working as intended.

mag missing configs and tests

For Automated CI

• Config one
  • Direct fastq input
• Config two
  • Single end data input #594
• Config three
  • krona (requires small database) Turned on in main config

For manual CI

Does not need a database

• Config four
  • CONCOCT (slow) #592

Datbases on AWS

• Config five (shared with below)
  • CAT
  • GTDB

Databases NOT on AWS

• Config five (shared with above)
  • CheckM (in CI but not in a config)
  • GUNC
  • Metaeuk

[prototaxites]

Metaeuk

For MetaEuk, specifying params.metaeuk_mmseqs_db = "UniProtKB/Swiss-Prot" only entails downloading a small database - doing a quick check, the fasta it's based on is only 87Mb. So that should potentially be feasible to run more automatedly?

[jfy133]

@prototaxites

Yeah that definitely should be feasible! Is it a single file with a public URL?

[prototaxites]

@prototaxites

Yeah that definitely should be feasible! Is it a single file with a public URL?

"UniProtKB/Swiss-Prot" is the string passed to the mmseqs databases command, which downloads the latest release of the database AFAIK. Now that I think about it, I'm not sure there's a way to specify a version, unfortunately, which limits reproducibility.

Alternative would be to specify the URL of a fasta file to --metaeuk_db - in the MetaEuk module test, I passed it the yeast .faa in the test-data repo: https://github.com/nf-core/modules/blob/master/tests/modules/nf-core/metaeuk/easypredict/main.nf, which seemed to work OK, but it might be better to find a prokaryotic file to use with the test data.

[jfy133]

List of tools that need to be somehow covered, where they are covered in currently:

tool	config	comment
adapterremoval	test_adapterremoval	maybe could be moved into ancient-dna, as they are people who mostly use it?
aria2
bbmap/bbnorm	test_bbnorm	Short test
bcftools	test_ancient_dna
cat
checkm
centrifuge	test
concoct
dastool
fastp	test
fastqc	test
freebayes	test_ancient_dna
genomad
gtdbtk
gunc
gunzip	test
krona	test
maxbin	test
metabat2	test
metaeuk	test_adapterremoval
mmseqs
multiqc	test
prodigal	test
prokka	test
pydamage	test_ancient_dna
samtools	test_ancient_dna
seqtk	test_bbnorm	Short test
tiara	test_adapterremoval	note has a special DASTOOL_FASTATOCONTIGBIN_TIARA process that doesn't actually run DASTOOL!
bowtie2 (phix)	test
bowtie2 (host)
bowtie2 (assembly)	test
busco	test
CAT
filtlong
kraken2	test
megahit	test
spades	test
spadeshybrid
nanolyse
nanopore
porechop
quast	test
tiara

Additional:

context	config
samplesheet input
assembly input

Got up to test_bbnorm, next is test_binrefinement