Continuous Delivery with Docker and Jenkins

Acceptance test-driven development

Acceptance tests, like most aspects of the Continuous Delivery process, are less about technology and more about people. The test quality depends on, of course, the engagement of users and developers, but also, what is maybe less intuitive, the time when the tests are created.

The last question to ask is, during which phase of the software development life cycle should the acceptance tests be prepared? Or to rephrase it, should we create acceptance tests before or after writing the code?

Technically speaking, the result is the same; the code is well-covered with both, unit and acceptance tests. However, it's tempting to consider writing tests first. The idea of TDD (test-driven development) can be well adapted ...