Summary
This concludes our example GitHub workflow run to showcase how we can integrate Karate into a CI/CD pipeline. For this purpose, we have addressed the writing of shell scripts, took a chance on Docker, and finally brought all the pieces of the puzzle together in a GitHub workflow. Also, we looked at how we can store reports and run our tests in GitHub workflows with native Maven.
As already mentioned, this chapter cannot, of course, provide a comprehensive introduction to this big topic but should rather show which pieces need to be put together to integrate tests into such an existing system. The exact steps may differ depending on which build server you are using, but this approach can be applied to all of them.
In Chapter 9, Karate UI for Browser Testing, we will look at a lesser-known part of Karate that allows you to write browser tests!
