On Thu, Jan 31, 2013 at 12:12 PM, Kris Borchers <kris(a)redhat.com> wrote:
I want to throw this out to the list for feedback. Something we have
been doing for a while now with the jQuery project is to require a unit test(s) for any PR
or change committed. This has worked very
well in two ways. First, it provides a built in way to see the issue being
fixed/implemented within the PR. That way, the reviewer doesn't have to build their
own test(s) to see if the issue being
addressed is actually fixed. Second, it helps prevent regressions down the road since
more of the code is covered by tests so you know if some change you think is unrelated
breaks something that
fixed days, weeks, years ago.
+1 most OS projects I worked on do that.
(besides for typos and other minor things)
I would like to suggest we make this policy for at least the JS library (since that is
the one I review most often) but I believe this policy would be useful across the entire
project. Let me know what
IMO this is a must, for all the bits.
Also... I'd strongly vote for supporting an (automated) integration
test suite (against a real server).
Mock testing is OK... but we should never forget about the real environment
aerogear-dev mailing list