From ant-dev-return-11909-apmail-jakarta-ant-dev-archive=jakarta.apache.org@jakarta.apache.org Sun Mar 25 14:32:39 2001 Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@jakarta.apache.org Received: (qmail 61168 invoked by uid 500); 25 Mar 2001 14:32:39 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk Reply-To: ant-dev@jakarta.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 61159 invoked from network); 25 Mar 2001 14:32:39 -0000 Message-ID: <011e01c0b539$3f19e980$0301a8c0@highland.st> From: "marvin greenberg" To: References: <005b01c0b51d$87d9c990$012a2a0a@nshome> Subject: Re: [VOTE] abstract goals and guidelines Date: Sun, 25 Mar 2001 09:38:24 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N > ----- Original Message ----- > From: "Stefan Bodewig" > To: > 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 *

Tests the functionality of VssgetTask, but cannot test full * capability because of limitations, dependencies, * */ If someone commits things with omitted or inadequate tests, with lame reasons for doing so, then they can be publically humiliated on ant-dev.