Guide to API Automation
A guide to how to perform API automation testing
API stands for application programming interface typically an API is used to facilitate the interaction between two different applications. The basic agenda of API testing is to check the request and response through the API are getting correctly or not.
Terms Related to API Automation:
HTTP Method: Hypertext Transfer Protocol (HTTP) is an application-layer protocol for transmitting hypermedia documents, such as HTML. It was designed for communication between web browsers and web servers, but it can also be used for other purposes.
The primary or most-commonly-used HTTP verbs (or methods, as they are properly called) are POST, GET, PUT, PATCH, and DELETE. These correspond to create, read, update, and delete (or CRUD) operations, respectively. There are a number of other verbs, too, but are utilized less frequently.
HTTP defines these standard status codes that can be used to convey the results of a client’s request. The status codes are divided into the five categories.
- 100: Informational – Communicates transfer protocol-level information.
- 200: Success – Indicates that the client’s request was accepted successfully.
- 300: Redirection – Indicates that the client must take some additional action in order to complete their request.
- 400: Client Error – This category of error status codes points the finger at clients.
- 500: Server Error – The server takes responsibility for these error status codes.