Return-Path: Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 28338 invoked by uid 500); 21 Jul 2003 11:58:10 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 28325 invoked from network); 21 Jul 2003 11:58:10 -0000 Received: from relay.t-intra.de (HELO relay.t-online-com.de) (62.156.147.74) by daedalus.apache.org with SMTP; 21 Jul 2003 11:58:10 -0000 Received: from DJ0X820J (p5080e7aa.dip0.t-ipconnect.de [80.128.231.170]) by relay.t-online-com.de (SMTPSVC(1.0.0.1)) with ESMTP id 2C1D6150031 for ; Mon, 21 Jul 2003 15:26:39 +0200 (CEST) Message-ID: <010101c34f7b$3173a4e0$020200c0@DJ0X820J> From: "Antoine Levy-Lambert" To: "Ant Developers List" References: <200307211315.43256.magiel@software-improvers.com> Subject: Re: Testing of Ant Date: Mon, 21 Jul 2003 13:28:21 +0200 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 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N 1. Do you use some kind of testing criterion? In other words, is there some kind of rule describing what should be tested? Examples of such a criterion could be: "every line of code should be executed during testing" or "every method should have at least one test case." Often such a criterion is referred to as code coverage criterion. There is no real rule. Testcases tend to be added to ant when problems have appeared, for instance to demonstrate that a change fixes a bug report from Bugzilla. In some instances, test cases are added proactively, to ensure that functionality will be preserved after a change. One of the problems with testcases is that a lot of tasks require specific external resources (databases, application servers, version control systems, SMTP mail server, ...) which do not always exist and do not exist under the same name everywhere. These tasks are often very badly covered by testcases. The situation is not ideal, but the current test suite runs on my PC under Win 2000 in approximatively 5 minutes and is giving a hint whether the current version of ant is OK or not. 2. Is the level of compliance to the testing criterion subject to measurement? In case of the first example, the percentage of lines executed during testing could be measured. Do you use a tool to automatically calculate your code coverage? Since there is no real rule, there is also no measurement. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org