Mark Derricutt's Disturbing Thoughts

My Top Tags

                                       

My Jaiku

Chrome Division – Doomsday Rider

Thursday, 21 August 2008 5:43 A GMT+12

1 Session per VM: Another Scaling Alternative

Wednesday, 20 August 2008 9:47 P GMT+12

The BGGA myth - Functional Java | Google Groups

Wednesday, 20 August 2008 7:33 A GMT+12

Spock's Beard – On A Perfect Day (live)

Wednesday, 20 August 2008 5:57 A GMT+12

Ola Bini: JtestR 0.3.1 Released

Tuesday, 19 August 2008 10:00 P GMT+12

Enslaved – Violet Dawning

Tuesday, 19 August 2008 6:14 A GMT+12

Distributed Messaging with Jetlang and Terracotta

Monday, 18 August 2008 10:17 P GMT+12

The Music of 2008 - week 33

Monday, 18 August 2008 8:57 A GMT+12

There Can Be Only One

Monday, 18 August 2008 8:10 A GMT+12

Search Box

 

Combining Test Regression Failure Reports

posted Thursday, 25 October 2007

After hacking away on some code/test changes yesterday I clicked the magic "commit" button and wandered off for a drink, a few minutes later I returned to find 60 or so "regression failure" comments against a bunch of JIRA tickets - turns out the tests passed from within IDEA but failed when ran from Ant and the build server.

I was happy to have had the immediate feedback of failing tests (although based on the anti-spam hate mail I received - not every one shared my happiness)., The problem stemmed from the fact the tests in question used TestNG's data provider support so JIRA was commented with failures for each iteration of the tests (plus the tests were related to multiple tickets).

Not wanting to receive any more hate mail from coworkers I hacked around a bit and altered the reporter to generate a nicer combined failure report:

Issues are now commented once per issue per stack trace, with the comment now also including test parameter information. I'm still not entirely happy with this thou as it still has the potential to generate a large number of comments/emails, an alternative idea I'm now considering is to create a new issue which includes all of test failures, parameters and stack traces in a single combined report, with JIRA issue links to the related issues. I'm thinking this will give the best of both worlds: automated regression feedback, centrally recorded feedback with context, low spam.

Now I just have to code it...

Technorati Tags: , , , ,

tags:          

links: digg this    del.icio.us    technorati    reddit