NbTestCase.noteWorkDir saves a copy of the workdir for a failed test. Similarly, JellyTestCase.captureScreen saves a screenshot of the application when the test failed. There are provisions to print a hyperlink to the log in case you are running inside Hudson and the test's work dir is inside the build's workspace.

These are useful, but much better would be to actually display these artifacts in the Hudson report. A new plugin promises to do just this.

The NbTC and JTC features should be rewritten to place files in the location this plugin expects. There is no need for an explicit dependency on Hudson information; rather, we need to somehow know

1. What the name of the top-level test being run is. Often getClass().getName() but may differ if a suite was initially run which loads some test cases in sequence, e.g. class.name = IDEValidation but we need to know IDECommitValidation. Not yet obvious how to determine this from the test JVM. Cannot be passed to <junit> because that is running many tests according to a patternset.

2. The location of the test's XML results, as opposed to the nbjunit work dir. Probably this would just need to be passed to the test JVM as a system property by common.xml.

Given these things, should be able to save a copy of workdir to ${test.whatever.results.dir}/${test.class.name} and it should be archived automatically if the right plugin is installed. Can then delete JTC.noteCaptureFile (just prints messages to log), and change NbTC.noteWorkDir to only call copytree.

Also need to double-check that existing jobs are configured to look for JUnit results as e.g. **/TEST-*.xml, rather than **/*.xml which could match unrelated XML files in the attachments.

Would be great if the plugin could be modified to set a flag, probably as an environment variable, in all builds when it was active. That way the copying in NbTC could take place iff it were running from a Hudson installation in which the plugin was active. As a first approximation, could disable the behavior if $HUDSON_HOME is unset.