beehive-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Eddie O'Neil <>
Subject removing gtlf dependency for controls testing -- was [Re: [jira] Updated: (BEEHIVE-906) Investigate removing GTLF DTD from controls test logs]
Date Sat, 03 Sep 2005 02:24:11 GMT

  This is a *great* step forward for us.  It means that we can remove
the gtlf DTD from the website as well.  I'll take going over this and
checking this in.

  For those who might be wondering, gtlf was a controls-specific way
of reporting test results.  In the end, it produces an HTML based
report that's similar to that produced by the
<junitreport> Ant task.  The tool has caused us some trouble with the
CC box because when the Beehive website goes down, the DTDs for an XML
file can't be found.  Removing this dependency and standardizing on
the usual JUnit tools makes the whole reporting process consistent
across Beehive.

  Personally, I don't see this as something to vote on, but if anyone
wants to consider this step more deeply, just say so.

  Comments / thoughts welcome...


On 9/2/05, Jacob Danner (JIRA) <> wrote:
>      [ ]
> Jacob Danner updated BEEHIVE-906:
> ---------------------------------
>     Attachment: gtlf_dtd_removed.patch
> I've attached a patch that will prevent  the DTD declaration from being placed in the
controls test output files.
> I verified it did not affect tests by passing the controls drts after these changes and
viewing the output files.
> > Investigate removing GTLF DTD from controls test logs
> > -----------------------------------------------------
> >
> >          Key: BEEHIVE-906
> >          URL:
> >      Project: Beehive
> >         Type: Improvement
> >   Components: Controls
> >     Reporter: Jacob Danner
> >     Priority: Minor
> >  Attachments: gtlf_dtd_removed.patch
> >

View raw message