News from the quality department

11 views
Skip to first unread message

Diogo Baeder

unread,
Aug 21, 2013, 3:54:55 AM8/21/13
to pr...@googlegroups.com
Hi there,

I've been working hard on raising our code coverage, and now we've just reached 100% LoC and code branch coverage. Also, I've set up our project for coveralls.io, and we have a nice little banner in the github page showing the current coverage:

Now, what means 100% code coverage for us, regarding how to face to project? It doesn't mean that the project is perfectly stable, or free of bugs - specially because this coverage uses test doubles when it has to hit the servers, making the tests more prone to false positives -. But it does mean that we have a much smaller chance to insert bugs at the first place, and it gives us a bigger safety net so that we can do more refactoring and redesigning, as we can now be less afraid of aggressive changes to the codebase.

Given the current situation, I've taken the liberty of creating a new challenge for us, by making this 100% our minimum code coverage for the build to pass, which means every part of the project must be covered by tests, otherwise it won't even pass. I've also changed from LoC (Lines of Code) coverage to branch coverage - which covers every code path for every condition block, following the cyclomatic complexity -. This is an experimentation, if we feel that it starts to be a burden for us to maintain the project then we can turn it off, or decrease the minimum coverage to a less aggresive threshold. However, I'd like us all to try to keep this up as much as we can, if possible. Let me know if you disagree with this approach.

Now, given the coverage we have, I'll start making some pretty aggressive refactoring sessions; We have lots of duplicated code throughout the project, and I want to extract them to base classes and neighbor objects, so to ease the path to fix bugs and implement new feature - also to make it easier to implement features that can be extended to different distributions -. Let me know if this causes any negative impact on your work, and we can sort a way out.

Cheers!
__________________________
Diogo Baeder
http://diogobaeder.com.br

Fernando

unread,
Aug 21, 2013, 7:43:30 AM8/21/13
to pr...@googlegroups.com
Awesome! Congratulations for the hard work.


--
You received this message because you are subscribed to the Google Groups "provy" group.
To unsubscribe from this group and stop receiving emails from it, send an email to provy+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.



--
http://about.me/fernandogrd

Bernardo Heynemann

unread,
Aug 21, 2013, 7:57:28 AM8/21/13
to provy
AWESOME!!!!!!!!!!!!!

Bernardo Heynemann
Developer @ globo.com
Reply all
Reply to author
Forward
0 new messages