Difference between revisions of "Software Testing"
Jump to navigation
Jump to search
m (→Module Tests) |
m |
||
Line 2: | Line 2: | ||
=Current State= | =Current State= | ||
==Test Resources== | |||
=== Common Test Resources === | |||
* Should be created together with SVN | |||
* Should be stored in one place (which one?) | |||
=== Specific Test Resources === | |||
are defined in module and saved in <code>src/test/resources</code> | |||
==Module Tests== | ==Module Tests== | ||
Line 28: | Line 36: | ||
</pre> | </pre> | ||
The existence of the required Interface test class can be checked later by parsing of pom.xml (e.g with command line utility) | 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 | * All other JUnit tests for the module are optional and should be presented in the separate test class | ||
Line 35: | Line 45: | ||
==Integration Tests== | ==Integration Tests== | ||
==GUI Tests== | ==GUI Tests== | ||
Selenium Tests | |||
==System Test== | ==System Test== | ||
Manual testing of Solutions by GUI & SVM Groups | |||
==Schedule== | |||
#Module Tests | |||
#Integration Tests | |||
# | |||
=References= | =References= | ||
[[Category:MDPL Developer|Software Testing]] | [[Category:MDPL Developer|Software Testing]] |
Revision as of 14:31, 22 June 2010
This page will describe the testing approach for the services and solutions developed at the MPDL.
Current State[edit]
Test Resources[edit]
Common Test Resources[edit]
- Should be created together with SVN
- Should be stored in one place (which one?)
Specific Test Resources[edit]
are defined in module and saved in src/test/resources
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)
- 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[edit]
GUI Tests[edit]
Selenium Tests
System Test[edit]
Manual testing of Solutions by GUI & SVM Groups
Schedule[edit]
- Module Tests
- Integration Tests