Difference between revisions of "Software Testing"
Jump to navigation
Jump to search
m |
m (→Module Tests) |
||
Line 11: | Line 11: | ||
example: src/test/java/CitationStyleHandlerInterfaceTest.java | example: src/test/java/CitationStyleHandlerInterfaceTest.java | ||
</pre> | </pre> | ||
** The class should be explicitely declared in the module pom.xml | |||
<pre> | |||
... | |||
<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> | |||
... | |||
</pre> | |||
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 | |||
* | |||
... | ... |
Revision as of 14:03, 22 June 2010
This page will describe the testing approach for the services and solutions developed at the MPDL.
Current State[edit]
Module Tests[edit]
- 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
...