Continuous Delivery with Docker and Jenkins

Comparing method 1 and method 2

To sum up, let's compare both solutions. The first approach is the real black-box testing from the user perspective in which Jenkins plays the role of a user. The advantage is that it's very close to what will be done in production; in the end, we will access containers via its Docker host. The second approach tests the application from the inside of another container. The solution is somehow more elegant and can be run locally in a simple way; however, it requires more files to create and does not call the application via its Docker host like it will be later done in production. 

In the next section, we step away from Docker and Jenkins and take a closer look at the process of writing the acceptance tests ...