Is your feature request related to a problem? Please describe.
Many wrappers are untested. This is not good. Writing tests for them en bloc will not work because of the sheer number. This must be tackled day by day.
Describe the solution you'd like
Write (at least) one wrapper test per work day.
Check if wrapper is still needed. If not then remove it. This counts as completion of the task for the day. ;)
Identify major use cases of wrapper. If there is more than one (e.g., single-end and paired-end mapping for read mappers) then complete both or add a note in the Notes section to this ticket or create a new ticket.
In some cases the wrapper may need to have some kind of restructuring, e.g., move some wrapper into sub directory or purge a sub directory (e.g., bwa/mem_pacbio).
In some cases it might be really hard to write a wrapper test. An example are the delly sub step test. Creating a ticket with detailed things to do counts as completion of the ticket.
It's allowed to write two tests a day to gain credit.
NB: large files should go into LFS!
Describe alternatives you've considered
The alternatives are leaving this untested or writing all tests at once. Both not desirable.
holtgrewe
commented
3 years ago
Is your feature request related to a problem? Please describe. Many wrappers are untested. This is not good. Writing tests for them en bloc will not work because of the sheer number. This must be tackled day by day.
Describe the solution you'd like Write (at least) one wrapper test per work day.
bwa/mem_pacbio).NB: large files should go into LFS!
Describe alternatives you've considered The alternatives are leaving this untested or writing all tests at once. Both not desirable.
Additional context N/A
Notes