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

Comments

Post a Comment

Popular posts from this blog

HTTP Payloads

Image
 What happens when I send a letter without information to the receiver that I require some details from them? What happens when the receiver writes a response to my letter without having the information I need? This information is similar to the body generally called a payload in HTTP request and response.  Let us see the payload in the HTTP request and HTTP response individually. I have added the below image to explain the HTTP request and response body/payload in JSON. I have used BurpSuite to take this image and Swagger Petstore (petstore.swagger.io) for this example. HTTP Request Payload Generally, the payload is not required for all the requests and responses. GET and HEAD methods usually do not require a body while sending a request to the server. The above example is a POST request to create a resource name 'doggie'. To achieve this, I should send some information about the resource which is called HTTP request payload. Breakdown of request payload: Content-Type:  ...
Read more

Hypermedia REST API

Image
Hypermedia is nothing but in simple terms it has hyperlinks associated with the API endpoint. It helps the API to link to related resources associated with the endpoint. This reduces the coupling between the server and the client. A hypermedia-driven REST API, often called a HATEOAS (Hypermedia As The Engine of Application State) API, utilizes hypermedia to enable dynamic interactions between clients and servers. In a hypermedia-driven API, clients navigate the API by following hyperlinks embedded within the responses received from the server, rather than relying on predefined URLs or endpoint structures.  Let me take an e-commerce online store as an example to explain more. When I search for a resource namely a product, it associates with its own API endpoint, links to 'Add to Cart', 'Save for Later', 'Buy Now', and 'Similar Products'. These connected links are called  Hypermedia links. I do not need multiple endpoints to refer to other endpoints becaus...
Read more