In the following section let us learn a little bit about the distributed build and testing. Imagine you have a really fat unit test or integration test suite. If you can divide them in small parts then you can run them in parallel. To run them in parallel you need multiple clones of your build/test machines. If you have them in place either using Docker or using some other mechanism, then the remaining thing to do is to make them a Jenkins slave agent.
The following illustration shows how a Jenkins pipeline to build, unit test and integration test utilizes the distributed build/test farm in Jenkins. You can see, we have two categories of Jenkins slave agents: Standalone Jenkins slave for build and unit test, and standalone Jenkins slave for integration test.
The unit testing is distributed across three Jenkins slave agents for build and unit test ...