UI and API tests friends again

UI tests and API tests are often done using different tools. Because the tools are so specialised it seems this is the right option. But in more complex scenarios both UI and API are entry points to systems under test. They are the "ends" in the end-to-end tests. So how to make that happen?

This time I will present the approach that is based on my experience that we are materialising in our open source frame work pumpo5.dev that is written in Java and expects tests to also be written in a simple Java code. You can check it out upfront. But the principles will be applicable to other frameworks as well. We will also discuss the why some tools are not really suitable for this approach. And answer the question if it means to get rid of those tools or not.