[Sugar-devel] Requiring test coverage for new code
Daniel Narvaez
dwnarvaez at gmail.com
Sun May 12 18:28:58 EDT 2013
Hello,
I'd like to propose to make it a requirement, enforced by code reviews, to
provide good test coverage when submitting new code. It will raise the bar
for contributions but it's essential if we want to improve quality (and I
think we have to). I can add a paragraph about it to sugar-docs, if we have
consensus.
A few details:
* What to do with patches which have been already submitted? I think it
really depends on the patch, so I'd leave it to the reviewer discretion.
* Should this apply to bug fixes? I tend to think it should, we are not in
a particularly active bug fixing period now, so it's a good time to start
with those too.
* Cannot apply to javascript code yet, because the infra is not in place.
Though writing the infra is on the short time priorities, so this should
change soon.
* Cannot apply to activities because we are missing infra bits. It would
not be too hard to add them, but I think we should focus on html activities
now.
--
Daniel Narvaez
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sugarlabs.org/archive/sugar-devel/attachments/20130513/8ea4a829/attachment.html>
More information about the Sugar-devel
mailing list