Return-Path: 
 <user-return-68182-apmail-ant-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-user-archive@www.apache.org
Received: (qmail 81127 invoked from network); 30 Jun 2009 16:35:07 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 30 Jun 2009 16:35:07 -0000
Received: (qmail 38048 invoked by uid 500); 30 Jun 2009 16:35:16 -0000
Delivered-To: apmail-ant-user-archive@ant.apache.org
Received: (qmail 37956 invoked by uid 500); 30 Jun 2009 16:35:16 -0000
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:user-unsubscribe@ant.apache.org>
List-Help: <mailto:user-help@ant.apache.org>
List-Post: <mailto:user@ant.apache.org>
List-Id: "Ant Users List" <user.ant.apache.org>
Reply-To: "Ant Users List" <user@ant.apache.org>
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 37946 invoked by uid 99); 30 Jun 2009 16:35:16 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jun 2009 16:35:16 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of ddevienne@gmail.com designates
 74.125.92.145 as permitted sender)
Received: from [74.125.92.145] (HELO qw-out-1920.google.com) (74.125.92.145)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jun 2009 16:35:07 +0000
Received: by qw-out-1920.google.com with SMTP id 4so111596qwk.10
        for <user@ant.apache.org>; Tue, 30 Jun 2009 09:34:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        bh=pgKjrdFV8wnvktBWK8i8m8PwP/1joBGkXsQNxbDjSjY=;
        b=ZgcPystIHCHrzEmpHp3r1sroyj9RBEj5a3D9VuNJ03rfMGWjHbXWcvLAw7MK0uMi8l
         EISduhqcFlpvyZA7YVLLiX/Nu/WE6gsNFtRYToqfXDaoB2/72oyeN9F5440W8VRYCaoi
         SuoLeFNfxFG8+MIcZNPuuotGncVM/N4O46kIc=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=AiZ7D7PVjaz0O3NziXvgZgBPf3HrHkIDcjHmwpltXIp+B6DUsQ05rzSFMwDuwgdeht
         9d1H4gYTBKutmGRZCxaS0WRN89kL2imhLDPLhf/vIYtbQcJ6y0gsl264J3cZ5FdLYLKv
         XOXyMz/UnxGN4WZfUzxaL0qKk0kZh4zKNTTMw=
MIME-Version: 1.0
Received: by 10.220.73.209 with SMTP id r17mr4302795vcj.46.1246379686413;
 Tue,
	30 Jun 2009 09:34:46 -0700 (PDT)
In-Reply-To: <e84cff280906300917j236fd163o6f73cf8606d9e189@mail.gmail.com>
References: <e84cff280906300917j236fd163o6f73cf8606d9e189@mail.gmail.com>
Date: Tue, 30 Jun 2009 11:34:46 -0500
Message-ID: <255d8d690906300934v7a8c639fr1b3e0404d4d18743@mail.gmail.com>
Subject: Re: Tests and Failures
From: Dominique Devienne <ddevienne@gmail.com>
To: Ant Users List <user@ant.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org

On Tue, Jun 30, 2009 at 11:17 AM, Tennis Smith<tennis@tripit.com> wrote:
> This is about ant used with cruisecontrol, but I thought someone here may
> know the answer. =A0Nobody seems to know on the cc mailer.
>
> I have a few tests that will be shown as "Tests: 0, Failures: 0, Errors: =
0,
> Duration: 0.0" in the dashboard's test suites report. =A0Generally, this =
is a
> poorly coded test or one that is commented out in the source. =A0So natur=
ally
> we'd like to know when that happens.
>
> How can I make ant/CC determine this is a failing test and report it that
> way?

AFAIK, the link between CC and Ant is via an XML log file, and XSL
stylesheets that massage this XML to generate something else like your
dashboard report. (that's also what <junitreport> does BTW). You must
then change the way the XML is processed to generate your dashboard
report to look for and flag those entries. How you do that depends on
how this info appears in the XML (as elements/attributes, or simply
text). To avoid interfering with the existing transformation to the
reports, you could add a pre-transformation converting your 0/0/0/0.0
entries into actual failures (the way "normal" failures are typically
reported in the XML), doing an XML to XML transform of just those
nodes for your special "empty" tests, and feed this document to the
dashboard/CC. You might also be able to do the same think directly on
the Ant side (maybe by altering XMLLogger?), although I don't know
where to start with this. Without more knowledge of the "pipeline"
used by CC these days, I can't suggest more. --DD

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org