diff options
| author |  uranther <jwheaton@purdue.edu> | 2009-07-14 17:09:39 -0400 |
|---|---|---|
| committer | uranther <jwheaton@purdue.edu> | 2009-07-14 17:09:39 -0400 |
| commit | e55693577ca32093b407824f2e5d38b258758f4d (patch) | |
| tree | 21597083fbc9b17b84fe419a9fed923d6121d5df /docs/CONTRIBUTING | |
| parent | 165dc493fdd02fee35ca266264367f2cd1db9599 (diff) | |
Added instructions in CONTRIBUTING to remind developers to write unit tests for bugfixes and new functionality
Diffstat (limited to 'docs/CONTRIBUTING')
| -rw-r--r-- | docs/CONTRIBUTING | 1 |
1 files changed, 1 insertions, 0 deletions
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. |