Continuous Delivery with Docker and Jenkins

Automating tests

The next step, usually much more difficult, is to prepare the automated tests for the system. It requires communicating with the QA team in order to understand how they currently test the software so that we can move everything into an automated acceptance test suite. This phase requires two steps:

• Acceptance/sanity test suite: We need to add automated tests that replace some of the regression activities of the QA team. Depending on the system, they can be provided as a black-box Selenium test or Cucumber test.
• (Virtual) test environments: At this point, we should be already thinking of the environments in which our tests would be run. Usually, the best solution to save resources and limit the number of machines required ...