The CI still contains a test for the prepare_inputs.py script. However, this script is no longer used and this function is transferred in the zarp-cli. I thus propose we remove it. @gypas@kanitz or anyone else in disagreement with this statement?
Edited
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
That above is a test for ALFA functionality that runs one-rule pipeline, correct?
I think we decided to move away from unit testing in zarp; if not - we will need to write such tests for every rule(?) But what about rules which do have their unit tests in their respective repositories (like TIN calculation or PCA plotting). Also - is this really our job to write such unit tests for: ALFA, STAR, cutadapt etc.?
I don't think we need them anymore. The example files in ALFA test were recently helpful when we had the discussion about directionality. But I guess this is also reported and saved in the corresponding issue and no additional files are needed.
Also, the test (at least ALFA) would need some adaptation because the structure changed. So from my side, I'm fine to remove this test.
As for the third test (since we are already discussing them all here and present our opinions):
If I recall correctly we decided to drop official support for LabKey parsing (we might have this internally, just not in the public repo). So, IMO, that script and test should be out too.