[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] Junit report for Subversion tests

From: Hyrum K. Wright <hyrum_at_hyrumwright.org>
Date: Thu, 22 Oct 2009 10:31:00 -0500

We've been using this to test a sample Hudson instance for Subversion
trunk and 1.6.x. I asked Bhuvan to send the patch here so I could +1
it to live in the repo. Version controlled, open source, useful for
posterity, and all that.

+1 to commit.

-Hyrum

On Oct 22, 2009, at 10:22 AM, Bhuvaneswaran A wrote:

> Hello,
> Please find attached a script to generate the Junit report based on
> Subversion test results. The junit reports can be used to integrate
> the
> Subversion build process with continuous integration tools like
> Hudson.
>
> [[
> New script to generate the junit reports for Subversion test cases.
> The
> junit reports can be used by continuous integration tools like Hudson
> for building and testing Subversion.
>
> * tools/dev/gen_junit_report.py
> The junit reports are generated by parsing the tests log file,
> tests.log. The test results, PASS, FAIL and SKIP are marked as
> appropriate in the junit reports. The XFAIL tests are considered as
> PASS. This script can take options: --log-file and --output-dir.
>
> The value for --log-file option denotes the log file to parse for
> generating the junit reports.
>
> The value for --output-dir option denotes the directory to store the
> junit reports. A separate file is created in this directory for each
> test case.
> ]]
> --
> Bhuvaneswaran A
> CollabNet Software P Ltd. | www.collab.net
>
> ------------------------------------------------------
> http://subversion.tigris.org/ds/viewMessage.do?
> dsForumId=462&dsMessageId=2410275<gen-junit.diff>

------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2410278
Received on 2009-10-22 17:31:34 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.