Software Testing

This page will describe the testing approach for the services and solutions developed at the MPDL.

Current State

Module Tests

• Interface Tests should have tests for all methods in the module interface (required)
  • Class Name convention:

     src/test/java/<name_of_module_interface>InterfaceTest.java
     example: src/test/java/CitationStyleHandlerInterfaceTest.java

• • The class should be explicitely declared in the module pom.xml

	...
	<plugin>
		<artifactId>maven-surefire-plugin</artifactId>
		<configuration>
			<skip>false</skip>
			<includes>
				<include>**/CitationStyleHandlerInterfaceTest.java</include>
				<!-- possible other test classes -->
				<include>**/TestCitationStylesSubstantial.java</include>
			</includes>
		</configuration>
	</plugin>
	...

The existence of the required Interface test class can be checked later by parsing of pom.xml (e.g with command line utility)

• All other JUnit tests for the module are optional and should be presented in the separate test class

...

Max Planck Digital Library

Graphical User Interface