When thinking about testing automation the popular movement in technology today is to automatically (forgive the pun) go full all in on a testing automation investment. However, not every technology or project necessarily needs a large-scale automation investment. The following represents some of our experience around when and how the decision to invest should be made.
The API can be compared with a waiter in a restaurant - it serves as a mediator between the one who orders food and the kitchen that prepares it. It delivers the order to the kitchen and then brings the dish to the client. The more customers there are in a restaurant, the more waiters are needed. In the same way, and as a rule, various people are involved in the development of the client and server. These are the Front-end and the Back- end Developers, each of which may use a different programming language.
Anyone who has built an API will know just how easy it is for a project to become disorganized and messy. Even if you use a document first workflow, things can feel a little clumsy, and so a solution that keeps control, but doesn’t get in the way of your flow could really make a difference.