GitLab

Changes:

* Add UseFixedSeed (bool switch) and fixedSeed Attribute values
  This allows to rerun the simulation with different but fixed seeds
  for random numbers.
* Add simulationSeed to save currently used seed while simulation is
  running. This is useful to determine the seed used for processor
  outputs in the output directory.
* Add Test for new version and refactor code duplicates
* Change Hash calculation to exclude UseFixedSeed, fixedSeed and
  simulationSeed to highlight (green) output to selected scenario
  within the gui.

Moved CI helper scripts to "Tools/ContinuousIntegration" and enabled Java assertions in POM files and helper scripts.

.gitlab-ci.yml:
- Refactored complete file: moved comment on top of file.
- Call helper scripts in "Tools/ContinuousIntegration" instead of just "Tools".

Tools/ContinuousIntegration/run_vadere_console_with_all_scenario_files.py:
- Execute scenario files alphabetically.
- Use "-enableassertions" when invoking Java.

POM files:
- Use "<enableAssertions>true</enableAssertions>" to be independent of SureFire's default settings.

In "pom.xml" files, added "failIfNoTests" to avoid that module is (wrongly) marked as error if no tests were executed.

Otherwise, a module is flagged as error if no unit tests were executed at all.

In "pom.xml" of "VadereGui", "VadereSimultor", "VadereState" and "VadereUtils", use version 2.19 of Surefire plugin to be able to skip tests via CLI.

Version 2.19 or higher of Surefire plugin allows to use following notation to skip tests:

  mvn test -Dtest=!LegacyTest

Note: maybe, use "mvn test -Dtest=\!LegacyTest" (with escape character) to avoid shell interpretation of exlemation mark.

Added coverage generation to "pom.xml" of following projects: VadereGui, VadereSimulator and VadereState

Now, coverage report is generated (under "<project>/target/site/coverage-reports/") when using

  mvn test