In order to verify and test Jupe we have two major strategies. The first is less technical and consists of the release policy, which can be outlined by the motto "release often, release early". We try to publish a new version of Jupe in a monthly rhythm and publish versions in an early alpha stage. Consequently, we can receive early feedback and realize bugs with the help of brave users.
Moreover, we use unittests with the JUnit testing framework written by Erich Gamma and Kent Beck [10]. There is a package structure parallel to the normal source directories that includes about 80 unittests. The most important parts of the plugin are covered by the tests, including the model, synchronization between source code and UML2, as well as some general plugin functionalities.
http://jupe.binaervarianz.de