JUnit has become a defacto standard for writing automatic tests for your java code ( ).Ī test case is specified for a single java class.

The above code is used in the de.analyser.tests plugin indicating tests that are specified for the de.analyser plugin. Such a host is specified in the manifest file with a property such as Fragment-Host: de.analyser They are not standalone projects but associated to a specified host plugin. To be able to provide unit tests also for packages and classes which are not published by the OSGi Bundle interface description, fragments have been introduced as a specific type of plugins. This article describes best practices for such test projects and how to integrate them into the Palladio Build Infrastructure.Īs mentioned before, test projects should be named like the plugin project they provide tests for, suffixed with '.tests' ('>.tests').Įclipse plugins are OSGi Bundles and provide a clear interface by explicitly defining the java packages accessible from other plugins / projects. A good practice to handle this is to place the JUnit tests within a separate eclipse projects named as the plugin project with the suffix '.tests'.įor Palladio development, we also use plugin tests for automated execution during Palladio Nightly builds. However, tests are not part of the software itself and for this, they should not be shipped with the plugin itself. To ensure a good code quality it is important to provide unit tests for the plugins as for any other java project.

Plugin JUnit TestsĮclipse plugins should be developed as seperate eclipse projects with the plugin id as project name.

Install junit in eclipse