Problem with Screen Snapshots using JUnit (again)

[Ben Waugh]

Hello All,

I'm seeing a problem that I see was reported by Jay Guidos on this
list on 30th April 2010, but I can't see any sign that this was
resolved. I am generating screenshots for failed tests using the
"festreport" Ant task, and this works OK, but prints "SEVERE" error
messages to the screen because it appears to be trying to write the
PNG files multiple times:

[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.46
sec
[festreport] Processing /home/waugh/sync/git-svn/SwingDemo/build/test/
report/TESTS-TestSuites.xml to /tmp/null1560390403
[festreport] Loading stylesheet jar:file:/home/waugh/sync/git-svn/
SwingDemo/test/lib/fest-swing-junit-1.2.jar!/org/fest/swing/junit/ant/
junit-frames.xsl
[festreport] 24-Jun-2011 23:53:05
org.fest.swing.junit.ant.ImageHandler decodeBase64AndSaveAsPng
[festreport] SEVERE: Unable to create the new file '/home/waugh/sync/
git-svn/SwingDemo/build/test/report/html/./
simplemvc.ControllerTest.clickController.png': a file was found with
the same path
[festreport] 24-Jun-2011 23:53:06
org.fest.swing.junit.ant.ImageHandler decodeBase64AndSaveAsPng
[festreport] SEVERE: Unable to create the new file '/home/waugh/sync/
git-svn/SwingDemo/build/test/report/html/simplemvc/
simplemvc.ControllerTest.clickController.png': a file was found with
the same path
[festreport] Transform time: 3651 ms
[festreport] Deleting: /tmp/null1560390403

To check that this isn't something stupid in my project I have created
a pretty minimal Swing demo application and test, but the problem is
still there. I have tried different versions of Apache Commons (1.3
and 1.4) and JUnit (4.5 and 4.6) and even built the latest FEST-Swing
from the Git repository, but none of these makes a difference.
Naturally I am checking that the destination directory has been
deleted before each trial.

I am using Oracle JDK 1.6.0_23 and Ant 1.7.1 on a machine running
Fedora 13.

Any help would be appreciated. As I say, the screenshots are actually
generated OK, but I a reluctant to check in a build file that
generates spurious warnings.

Best regards
Ben