An important part of
UnitTestingGuis is not to have to. Seriously, GUIs should be as thin and contain as little logic as possible. If the GUI additionally is only loosely coupled to the business logic (via ModelViewController or ModelViewPresenter),
UnitTestingGuis should become rather simple.
A good example on
testing Swing UIs with pure
JUnit can be found at
http://www.xp123.com/xplor/xp0001/index.shtml
If you still need to write more complicated tests, take a look at
http://jfcunit.sourceforge.net/
related forum threads:
https://coderanch.com/t/94802/Testing/help-abbot-test-java-swing
other resource:
http://www.objectmentor.com/resources/articles/TheHumbleDialogBox.pdf