How would you approach API exploratory testing?

 This question was asked during 30 days of API Testing in the Ministry of Testing.

I have used https://excalidraw.com/ to share my thoughts.




Let me know your suggestions for improvement or comments!



Comments

Post a Comment

Popular posts from this blog

Telnet: Connecting the Dots. Why it still matters today?

Every time I connect to a remote server with Telnet, I'm reminded how this vintage yet powerful tool unlocks a complex dance between IPv4 and IPv6 addresses that keeps the digital world connected. Software engineers and network administrators have used Telnet to peek behind the scenes of computers far away. Telnet works like a simple phone call over the internet to a remote computer. By typing a straightforward command like           telnet <ip address of remote computer> <port number> I can connect to that computer and check which ports are open and listening.  IP addresses come in two flavors: IPv4 and IPv6. Think of IPv4 as a classic phone line and IPv6 as a modern digital line. When I use a hostname instead of an IP address, Telnet asks the Internet's directory (DNS) for both IPv4 and IPv6 addresses. Telnet usually tries to connect to modern IPv6 first. If it is not reachable or the line is busy, it falls back to the trusty IPv4 classic line...
Read more

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 - Why? - II (Part 5)

Let's continue the previous post to understand further why we need testing for embedded systems. Some might not know this, some might have experienced it, some might have tried it, and some might have been experts. What am I talking about? The process of baking bread in the oven. How many of us tried this at least once in our lifetime?  Imagine a situation, where you have set the timer for 30 seconds (no bread will be baked in 30 seconds, this is just an example 😊) but due to a software error, the timer mistakenly interprets this as 30 minutes. What is the outcome? Burnt bread, wasted ingredients, and frustration. Now imagine the temperature was set with the assumption of 100 degrees Fahrenheit but the oven was programmed to interpret it as Celcius. You would end up with underbaked dough instead of golden-brown perfection. How does the baked bread come out well if the expected outcome does not meet the requirements? These seemingly small errors arise from a lack of software testi...
Read more