Chapter 7. End-to-end testing
This chapter covers
- End-to-end testing of microservice applications
- Tools for end-to-end testing
- Setting up Arquillian for end-to-end tests
End-to-end tests build on integration tests, which in turn build on all the other forms of testing you’ve learned about. As the name indicates, end-to-end tests are designed to test your application from start to finish (or top to bottom, if you prefer). They should in theory simulate a real-world user of your application, or at least perform the actions of a real user. In practice, these tests are usually the most difficult to write and consume the most development time. End-to-end tests are nearly always slow in comparison to other types of tests, so they’re often isolated from the usual development process—on a Jenkins build server, for example (https://jenkins.io).
Note
Learning everything about continuous integration and delivery would be beyond the scope of this book, so we’re thinking there may be another mini book in the pipeline. (For those familiar with the topic, excuse the pun.) That said, to get you started, chapter 10 provides a reasonably detailed discussion of how to set up a deployment pipeline using Jenkins.