Regarding the TestNG side of things - a little hack I whipped up awhile ago for this sort of thing is here:
http://www.talios.com/automated_test_regression_reporting_with_testng_and_jira.htm Whilst not ideal in its current form (repeated jira comments on each failure) I find the idea quite useful, although I'm not running it against my $work code just yet. A TestNG listener watches for failed tests, and if the test has an associated @RelatedIssue annotation the JIRA ticket is commented with the failure stacktrace. Currently in my code I'm just added @RelatedIssue annotations whenever I add @Test's that relate to a particular issue. Mark On 5/29/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote:
Also, please note that when we move to JDK 1.5, we can put this discussion to rest, as we can annotate our tests to not run (JUnit 4.x). They will then be reported as skipped tests and not end up in oblivion. TestNG is also a possibility, but I overheard that the maven surefire plugin is not up to par.
