public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Pedro Izecksohn <izecksohn@yahoo.com>
Cc: mauve-discuss@sources.redhat.com, Chris Burdess <dog@bluezoo.org>
Subject: Re: Proposed Mauve test: childNodesLength
Date: Mon, 16 Jan 2006 15:15:00 -0000	[thread overview]
Message-ID: <1137424497.8135.10.camel@localhost.localdomain> (raw)
In-Reply-To: <200601160047.59642.izecksohn@yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]

Hi Pedro,

On Mon, 2006-01-16 at 00:47 -0400, Pedro Izecksohn wrote:
> Two files are attached.

Thanks! I have committed them as follows:

2006-01-16  Pedro Izecksohn  <izecksohn@yahoo.com>

        * gnu/testlet/org/w3c/dom/childNodesLength.java: New test.
        * gnu/testlet/org/w3c/dom/test.xml: New data file.

Of course a couple of these tests still fail against GNU Classpath dom
implementation till we get your patch for that in.

BTW. We are trying to setup the DOM test suites are at

    http://www.w3.org/DOM/Test/

We currently test against Level 3 Core (although we could test
against Level 2 HTML and Level 3 Load and Save as well).

See our current results at:
http://builder.classpath.org/xml/dom.html

It would be ideal if we can turn these tests into mauve like PASS/FAIL
results. Then we can more easily create automatic regression reports
with the existing scripts on builder.classpath.org.

Maybe you are interesting at looking at the tests and the results (we
still have a lot of failures there)?

Cheers,

Mark

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2006-01-16 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-16  2:46 Pedro Izecksohn
2006-01-16 15:15 ` Mark Wielaard [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1137424497.8135.10.camel@localhost.localdomain \
    --to=mark@klomp.org \
    --cc=dog@bluezoo.org \
    --cc=izecksohn@yahoo.com \
    --cc=mauve-discuss@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).