So as anyone who has peeked at the Do source tree knows we've got a severe lack of tests. We've seen the effects of this issue with some bugs reoccurring multiple times (think Do crashes when switching from Docky). At this I propose we require tests with new commits. We'll have to hash out some guidelines as to when a commit requires tests, I'd think that some commits are small enough that a test wouldn't make sense. At some point we should go back and add tests where we're missing them (basically everywhere), but we can at least stop adding new stuff without tests. What do people think, can we make this a new development guideline and merge requirement?
-- --Alex Launi --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GNOME Do" 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/gnome-do?hl=en -~----------~----~----~----~------~----~------~--~---
