|
|
|
## Why do we test?
|
|
|
|
* To find errors early,
|
|
|
|
* to facilitate future enhancements of FAME,
|
|
|
|
* to improve scientific transparency of FAME-based models,
|
|
|
|
* and to improve scientific reproducibility of FAME-based models.
|
|
|
|
|
|
|
|
## What do we test?
|
|
|
|
We extensively employ unit tests (i.e. test of functions / units of work) and sometimes integration tests (i.e. test of module interactions).
|
|
|
|
We aim at a 100% coverage of meaningful code (i.e. trivial code like getters & setters).
|
|
|
|
|
|
|
|
## How do we test?
|
|
|
|
* Use Junit & mockito for Java, pytest and mockito for Python.
|
|
|
|
* Test-Cases are to be placed in separate folder structure.
|
|
|
|
* Scripts are provided to run all unit tests with "one button".
|
|
|
|
* All tests are executed, even if individual tests do not work.
|
|
|
|
* We use coverage analysis to find uncovered code segments. |
|
|
\ No newline at end of file |
