> ----- Original Message ----- > From: "Stefan Bodewig" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, March 21, 2001 6:27 PM > Subject: [VOTE] abstract goals and guidelines > > > +1 for all, except > > > * no commit of new features without testcases > > -1 unless someone tells me how to really provide a testcase for something > like vssget (or is checking the accepted and rejected attributes really > enough and testing the functionality is not required?)
I'd say the rule with all rules is that you can always break it if you come up with a credible reason for the exception. I don't know the details of the issue with vssget, but, e.g., /** * VssgetTest * <p>Tests the functionality of VssgetTask, but cannot test full * capability because of limitations, dependencies, * <your reason here> */ If someone commits things with omitted or inadequate tests, with lame reasons for doing so, then they can be publically humiliated on ant-dev.
