I remember reading an old Sequel release announcement on RubyForum, where there was an implication that Sequel had 100% code coverage. I'm not sure if this was true, though I don't doubt it. In any case, I finally decided to run the specs with coverage, and found that despite not checking coverage in the entire time I've been maintaining Sequel, we were doing pretty well (about 94% coverage).
As a result of a lot of patches today, Sequel now has 100% code coverage for all files. Along the way, many specs were added, and a few bugs fixed. Note that 100% code coverage is line coverage only, not statement coverage, branch coverage, path coverage, or combinatorial coverage. Also, remember that specs may have bugs, and just because a line is covered doesn't mean it is fully tested. That being said, I think Sequel is doing fairly well in terms of bugs, in the core/model code at least. Most of the future testing will focus on the integration test suite, to make Sequel works with real databases. As always, I welcome patches. Jeremy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en -~----------~----~----~----~------~----~------~--~---
