From e55693577ca32093b407824f2e5d38b258758f4d Mon Sep 17 00:00:00 2001 From: uranther Date: Tue, 14 Jul 2009 17:09:39 -0400 Subject: Added instructions in CONTRIBUTING to remind developers to write unit tests for bugfixes and new functionality --- docs/CONTRIBUTING | 1 + 1 file changed, 1 insertion(+) (limited to 'docs') diff --git a/docs/CONTRIBUTING b/docs/CONTRIBUTING index f5d7ebc..9032b42 100644 --- a/docs/CONTRIBUTING +++ b/docs/CONTRIBUTING @@ -66,6 +66,7 @@ This is a relatively easy, solid and transparent way to handle all requests in o we know for bigger changes this is not always feasible. Just try to keep the merges about bigger "clean changesets". * Your code should not introduce any compile warnings or errors. And also, no regressions but that's harder to check. +* Unit tests should be written to verify bug fixes and new functionality. That said, you can always ask us to check on your stuff or ask for advice. -- cgit v1.2.3