Summary

Now that we've taken a look at jfcUnit and what it can do, what does it offer over the other testing frameworks?

Tight JUnit integration: jfcUnit extends the JUnit TestCase class and adds in the necessary pieces for you to test your Swing app right JUnit.
Ease of use: As we've seen, it is relatively easy to grab the appropriate component using the ComponentFinder.
Easy component testing: jfcUnit's TestHelper class offers us several methods to aid us in testing our interfaces with mouse clicks and drags, mouse wheel movements, and text entry. This wide variety of simulations is enough to perform most test cases available.
XML Tests: jfcUnit also offers the ability to record and perform tests on your classes using an XML testing file. We didn't cover here because we felt the support for pure Java is currently superior to the XML support; hopefully this will improve in future releases of jfcUnit. For more information on the XML part of jfcUnit go to http://jfcunit.sf.net/jfcunitxml.htm

What are some of the disadvantages of jfcUnit?

Functionality Testing: If you are looking for more functionality testing versus unit testing, Jemmy may be a better choice.