Ovid wrote: > --- Moritz Lenz <[EMAIL PROTECTED]> wrote: > >> Attached is an updated version, as well as an example chart it >> creates. >> This is not as pretty as the previous version, but it's more >> informative. >> If there are significant number of failed tests, I could also include >> their number. >> >> Any comments? > > Looks great.
Thanks ;-) > However, from a testing perspective, I'm wondering why > there is such a huge number of skipped tasks. Shouldn't those be TODO > tasks? Mostly because the skipped tests are parse failures or throw runtime errors, because crucial parts are not yet implemented in the compiler. > Skips are really easy to ignore and it's virtually impossible > to know if they'll ever pass but TODO tests unexpectedly succeeding > tend to stand out. That's really a problem, and atm the only thing you can do is run the test suite without fudging at all. But that only works well when no tests in a file bail out. Other solutions I can think of are: * make fudge wrap skipped tests in eval-blocks and mark them as TODO. Don't know if that's doable without breaking too much * move offending tests to separate files (much work, and don't know if that's a good solution in the long term) * Implement all missing features. .oO( ... ) Cheers, Moritz -- Moritz Lenz http://moritz.faui2k3.org/ | http://perl-6.de/
