As we are adding more and more functional tests our build is taking quite a bit of time which will make it harder to have fast feedback loops (either locally or on the CI server). It bumped from ~4:30min to above 7 on my local machine:
[INFO] Reactor Summary:
[INFO]
[INFO] Smart testing ...................................... SUCCESS [ 0.727 s]
[INFO] smart-testing-core ................................. SUCCESS [ 13.491 s]
[INFO] junit-test-result-parser ........................... SUCCESS [ 1.728 s]
[INFO] smart-testing-surefire-provider .................... SUCCESS [ 7.337 s]
[INFO] smart-testing-strategy-changed ..................... SUCCESS [ 4.464 s]
[INFO] smart-testing-strategy-affected .................... SUCCESS [ 9.435 s]
[INFO] smart-testing-strategy-failed ...................... SUCCESS [ 2.511 s]
[INFO] smart-testing-maven-lifecycle-extension ............ SUCCESS [ 4.022 s]
[INFO] smart-testing-test-bed ............................. SUCCESS [07:17 min]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 07:49 min (Wall Clock)
[INFO] Finished at: 2017-09-05T22:17:52+02:00
[INFO] Final Memory: 40M/1385M
[INFO] ------------------------------------------------------------------------
We should review our Test Bed tests in order to:
- minimize redundant/overlapping tests
- identify those which we could test in isolation (unit tests)
- narrow the builds for only relevant modules, e.g.
.build("config/impl-base") where necessary
As we are adding more and more functional tests our build is taking quite a bit of time which will make it harder to have fast feedback loops (either locally or on the CI server). It bumped from ~4:30min to above 7 on my local machine:
We should review our Test Bed tests in order to:
.build("config/impl-base")where necessary