I've also used the technique of generating xUnit formatted reports from the shell script and having Jenkins pick those up. Required the xUnit plug-in if I recall.
Ben On Dec 7, 2012 8:56 AM, "Matt Benson" <gudnabr...@gmail.com> wrote: > Bill: You might also consider Antunit [1] for a simple means of > generating JUnit-compatible XML. > > HTH, > Matt > [1] http://ant.apache.org/antlibs/antunit/index.html > > > On Fri, Dec 7, 2012 at 10:35 AM, Anthony Shortland < > anth...@dtosolutions.com> wrote: > >> Hi Bill, >> >> Are you aware of Rerun (http://rerun.github.com/rerun) and its ability >> to formally manage shell script test cases? >> >> Anthony. >> >> Sent from my iPhone >> >> On Dec 7, 2012, at 7:48 AM, Bill Trost <tr...@cloud.rain.com> wrote: >> >> Hi, >> >> I need to run a set of unit tests that simply consist of seeing if >> two files are identical. There are all kinds of Unix tools (diff, >> cmp, comm, etc.) that can provide the basic information, but how do >> I translate that into unit test results that Jenkins can understand >> and display? Simply emitting XML for xUnit parser seems a bit crude. >> >> Thanks, >> Bill >> >> >
