From: Anthony Balkissoon <abalkiss@redhat.com>
To: mauve-patches@sources.redhat.com
Subject: Harness XML output improvements
Date: Mon, 19 Jun 2006 22:09:00 -0000 [thread overview]
Message-ID: <1150754929.25174.62.camel@tony.toronto.redhat.com> (raw)
This patch improves the XML output from the Harness to be as verbose as
the standard output. Includes line numbers for passes and fails, and
stack traces for uncaught exceptions.
2006-06-19 Anthony Balkissoon <abalkiss@redhat.com>
* RunnerProcess.java:
(lastFailureMessage): New field.
(runtest): Strip the "gnu.testlet" from the name passed to the
TestResult. Also use the new 3 parameter TestResult.addException to
pass the stack trace to the TestResult. Properly indent the stack
trace when printing exception details.
(getStackTraceString): New method.
(fail): Get the description from check2 and add the full failure
string to the TestResult.
(check(Object, Object)): Likewise.
(check(boolean, boolean)): Likewise.
(check(int, int)): Likewise.
(check(long, long)): Likewise.
(check(boolean)): Likewise.
(check2): Return the description. Do not add the failure description
to the TestResult here, do it in the individual check() methods so that
a full description can be added. Use the new TestResult.addPass(String)
method instead of the old no argument method.
* TestReport.java:
(writeXML): Do not write the passCount value, write the passes as well
as the fails, and write the stack traces for exceptions. Properly
indent the xml.
* TestResult.java:
(passCount): Removed this field.
(passMessages): New field.
(exceptionReason): New field.
(addPass): Now takes in a String argument, acts just like addFail().
Descriptions are taken in for passes as well as fails.
(addException): Now takes 3 arguments instead of 2, the new argument is
the stack trace for the exception.
(getPassCount): Returns the size of the passMessages ArrayList.
(getPassMessages): New method.
(getExceptionReason): Likewise.
--Tony
reply other threads:[~2006-06-19 22:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1150754929.25174.62.camel@tony.toronto.redhat.com \
--to=abalkiss@redhat.com \
--cc=mauve-patches@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).