public inbox for mauve-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@kernel.org>
To: James Ahmed <crystalera123us@gmail.com>
Cc: ptisnovs@redhat.com, mauve-discuss@sourceware.org
Subject: Re: mauve Harness and RunnerProcess Proposal
Date: Sun, 12 Feb 2012 09:59:00 -0000	[thread overview]
Message-ID: <1329040737.13624.54.camel@jaguar> (raw)
In-Reply-To: <CAMMvJZtKUBEQHXvJaPWf4b51hRAHxWnA4hpuxCZkuSSsGtw2CQ@mail.gmail.com>

(CC'ing the mailing list.)

On Sat, 2012-02-11 at 16:51 +0000, James Ahmed wrote:
> Hi there, 
> 
> 
>          I recently started using the Mauve testcases on a Custom JVM.
>         And i noticed a small little feature i thought would be a
>         great addition to the Project.
>         For better automation, test cases should create an xml file
>         based on their file name.
>         
>         
>         So for instance a command line option "-autoXml <results_dir>"
>         would create xml files containing the results of the test runs
>         in the <results_dir> specidied.
>         
>         
>         so running testcase java/beans/XMLDecoder/EqualityChecker.java
>         would create 
>         <results_dir>/java/beans/XMLDecoder/EqualityChecker.xml
>         so running java.*
>         would populate the relevant xml files in their relevant
>         locations.
>         
>         
>         The argument here is that this will help automated testers
>         gather the results more efficiently?
>         
>         
>         I would like to know if  this change would be accepted before
>         i began making it.

If Mauve doesn't already support this sort of thing, it certainly makes
sense to me to add it.

			Pekka


           reply	other threads:[~2012-02-12  9:59 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAMMvJZtKUBEQHXvJaPWf4b51hRAHxWnA4hpuxCZkuSSsGtw2CQ@mail.gmail.com>]

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=1329040737.13624.54.camel@jaguar \
    --to=penberg@kernel.org \
    --cc=crystalera123us@gmail.com \
    --cc=mauve-discuss@sourceware.org \
    --cc=ptisnovs@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).