Essential Checklist for HTTP Requests in API Testing

 

This is an attempt to remind you what needs to be checked while sending and retrieving data from an HTTP request in API testing.



  1. Method - Ensure the appropriate method (GET, POST, PUT, DELETE, etc.) has been selected to send the request using any tools like Postman, SOAPUI, or Swagger.
  2. Host - The host plays a crucial role in hitting the exact server the user wants for the operation.
  3. Version of API - The version should be known before hitting the request. It helps to process the data in the deserved endpoint.
  4. Path - When the path is provided in the way where exact data is to be stored or updated, it reaches the destination correctly.
  5. Endpoint - It is the destination point. Though the entire direction is correct, if the request does not have an accurate endpoint, it leads to retrieving inappropriate data and is time-consuming.
  6. Request Payload - Payload is the data provided to the server to process the request correctly.
  7. Request Headers - It is crucial for communication between the client (Eg. Browser) and the server. Verify the request headers to understand the data flow if the system passes the valid data. Some of the commonly used headers are HTTP version, Accept, Accept-Language, User-Agent, Authorization, and Cache-Control.
  8. Response Status code - Verify the status code whether the exact code is displayed and whether the corresponding messages are delivered for easy understanding.
  9. Response data - Requested data should be processed and responded to by the client from the server without any malfunction or deviation from what was asked.
  10. What should I test? - Most importantly, one should know what should be tested based on the request. It relies on understanding the requirements and proper communication between the testers and others from the team.

Comments

Post a Comment

Popular posts from this blog

Embedded testing - Introduction (Part 1)

 I'm writing a series about my recent learnings in embedded testing. Here is the basic introduction about this topic with a simple example. Scenario 1: A patient books an online appointment to provide a blood sample for a hemoglobin level test. To book an appointment, the patient only needs access to a web or mobile application. When a quality engineer tests the functionality of this appointment registration process, it is referred to as software testing. Scenario 2: The patient now wants to collect the test report after the blood sample analysis. To measure the hemoglobin level, the lab technician uses an automated medical device. At this stage, if the quality engineer is involved in testing, they require both a physical device (hardware) to process the sample and an application (software) to enter or capture the details. When testing involves both hardware and software, it is referred to as embedded testing. Click here to read the next blog
Read more

Embedded testing - Embedded system (Part 2)

Image
 In this second blog post related to embedded testing, firstly I would like to explain an embedded system. Click here to view the first post. What does embedded mean? It is something integrated into another thing. For example, an embedded hyperlink is text that acts as a link instead of an actual link ( https://www.google.com can be  Google ) . Embedded content is content used in a website from another source. When you attach an Excel sheet to the PowerPoint presentation, it is called an embedded file. An embedded system is a device that incorporates all the relevant components such as a microprocessor, microcontroller, memory, input/output units, drivers, bus, and many more. The embedded system is designed to work with a combination of hardware and software to perform specific tasks to achieve functionalities within a larger system. If a human user of a system is only partially aware that they are interacting with a computer running software, then it is an embedded sof...
Read more

Embedded testing - Embedded software (Part 3)

 In continuation of the previous post, " Embedded system ," let's examine embedded software and how it plays a major role in physical devices. An application software is a computer program that provides functionality on a computer. It is specifically made for consumers to use. However, embedded software is computer software that is written for controlling physical machines to operate. Most of the embedded software is written in C, C++, and C#. In recent times, Javascript, Java, and Python also come into the picture to control embedded systems. Embedded software is like a well-organized but strict boss living inside the machine or device. It is tiny, invisible, and works behind the scenes to make sure the machine does not crash. How does the embedded software work? Embedded software is a manager who sits in the office and manages the team (hardware) Providing instructions:  This manager never calms down and he/she keeps on giving instructions to the team.  To check the tem...
Read more