The current CI Actions only build Comet and try if the output to the command writing a new parameter file works.
It would be great if the CI would test the binaries for their main function with a small dataset and test if the outputs are as expected. This would allow regression tests for errors like the missing deltaCn calculation with one of the search configurations.
I have a local smallish example that runs in 0.0 seconds with comet and weighs 22.6 MB which is an extract of the ProteoBench DDA QExactive Dataset and FASTA file. I think this would serve as a nice starting point to add End-to-End testing.
The current CI Actions only build Comet and try if the output to the command writing a new parameter file works.
It would be great if the CI would test the binaries for their main function with a small dataset and test if the outputs are as expected. This would allow regression tests for errors like the missing deltaCn calculation with one of the search configurations.
I have a local smallish example that runs in 0.0 seconds with comet and weighs 22.6 MB which is an extract of the ProteoBench DDA QExactive Dataset and FASTA file. I think this would serve as a nice starting point to add End-to-End testing.