mattwynne
commented
12 years ago See https://github.com/ghnatiuk/continuous_coverage_test for @ghnatiuk's kind attempt to extend Ruby 1.9's built-in coverage API to work for us.
Also relevant to #6
Open mattwynne opened 12 years ago
mattwynne
commented
12 years ago See https://github.com/ghnatiuk/continuous_coverage_test for @ghnatiuk's kind attempt to extend Ruby 1.9's built-in coverage API to work for us.
Also relevant to #6
I just got a first implementation of darts running, and I can it over the relish specs. Good news is it ran without any errors, and seems to have collected accurate information. Bad news is it was very slow.
A spec suite that already takes 79 seconds took just over 800 when run with darts.
Which makes it almost no use.
I think a quick win here is that I misunderstood how RSpec's after(:all) hook works, and I've been saving the mappings after every example. First thing to do is remove that and see how that improves things.
I've also been playing around with the new Coverage interface in Ruby 1.9. Out of the box it won't work for Darts, as it assumes a single coverage run per process, but we might be able to write a little bit of C to alter that.