Software Testing

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

Test Resources

Common Test Resources

• Should be created together with SVM
• Should be stored in one place (which one?)

Specific Test Resources

• To be defined individually by each module and saved in src/test/resources

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)

• • How to define scope of parameter values of tested interfaces ???

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

Integration Tests

Technical Integration

• REST interfaces
• EJB interfaces

Logical Integration

• Functionality tests (JUnit)
• Selenium tests (GUI)
  • See for PubMan

System Test

Manual testing of Solutions by GUI & SVM Groups

Bug Testing

Critical (regularly occurring) bugs should be identified together with SVN and tested with the specific Test (Selenium or JUnit), on hand of its nature.

Schedule

1. Module Tests
2. Integration Tests

   ...

3. Bug testing

Max Planck Digital Library

Support Vector Machine

Representational State Transfer

Enterprise JavaBeans

Graphical User Interface

Apache Subversion