There are several open tickets with testneeded label and it would be nice to close them with tests. In whateverable I mainly do system testing, so every test is a command that is sent to the bot on an actual IRC server. While some would consider this approach improper (at least when used alone without unit tests), I feel more comfortable knowing that the functionality is tested thoroughly in an exhaustive manner. This helped me reveal memory issues, left file handles, segfaults and other issues in rakudo from whateverable test suite. Maybe something like that should be implemented for sake also (i.e. a testing framework that runs actual Sakefiles, looks at results and cleans up).
There are several open tickets with
testneededlabel and it would be nice to close them with tests. In whateverable I mainly do system testing, so every test is a command that is sent to the bot on an actual IRC server. While some would consider this approach improper (at least when used alone without unit tests), I feel more comfortable knowing that the functionality is tested thoroughly in an exhaustive manner. This helped me reveal memory issues, left file handles, segfaults and other issues in rakudo from whateverable test suite. Maybe something like that should be implemented for sake also (i.e. a testing framework that runs actual Sakefiles, looks at results and cleans up).