Here are some sample answers to the questions presented in this chapter:
- Pros and cons:
- Pro: We don't need to have the particular shell, tool, or language required by the task installed on our host.
- Pro: We can run on any Docker host, from Raspberry Pi to a mainframe computer; the only requirement is that the host can run containers.
- Pro: After a successful run, the tool is removed without leaving any traces from the host when the container is removed.
- Con: We need to have Docker installed on the host.
- Con: The user needs to have a basic understanding of Docker containers.
- Con: Use of the tool is a bit more indirect than when using it natively.
- Running tests in a container has the following advantages:
- They run equally well on a developer machine than on a test or CI system.
- It is easier to start each test run with the same initial conditions...