Jesper Findahl

I moved the diagrams to https://github.com/VincenzoFerme/benchflow-temporary-documentation/tree/master/roadmap/Jesper/architecture/diagrams/svg so that they are easier to generate and view. I think the changes are incorporate there with details, except how we schedule which maybe...

I think we have already done this.

@igormoreno ok - try with this commit https://github.com/benchflow/benchflow/pull/266/commits/b4f8adb9ac869c47bd799d03d971161bbd41fc31

@igormoreno this is how you organize imports for IntelliJ https://www.jetbrains.com/help/idea/2017.1/optimizing-imports.html#d878663e56

We should include dependencies from BenchFlow in this way: ``` ... ... ${project.basedir} ... benchflow-dsl feature-dsl-demo-conversion_046e8d 0.1.0 ... benchflow-faban-client devel_ad148a 0.1.0 ... 1.3.0 2.5.2 ... ... cloud.benchflow benchflow-dsl ${benchflow-dsl-jar.version} cloud.benchflow...

To properly fetch the dependencies it is necessary to explicitly call phases (defined above) like so ` mvn clean post-clean compile`. To simplify this into one command we added the...

Fixed in experiment-manager in https://github.com/benchflow/benchflow/pull/291

I think these dependencies have been removed since we moved to one-repo. We need to fetch them as described above.

Can also be found in the [documentation](https://github.com/VincenzoFerme/benchflow-temporary-documentation/blob/master/development/testing/testing-overview.md): - https://martinfowler.com/articles/microservice-testing/ - https://github.com/palantir/docker-compose-rule how things are done in the experiment-manager: - https://github.com/benchflow/benchflow/blob/devel/benchflow-experiment-manager/application/src/test/java/cloud/benchflow/experimentmanager/BenchFlowExperimentManagerApplicationIT.java

I suggest that we follow the API standard as agreed for the test-manager and experiment-manager by resource based. See https://github.com/benchflow/benchflow/tree/devel/benchflow-test-manager/application/src/main/java/cloud/benchflow/testmanager/resources