Postman - API Testing Tool in Hindi Session#01- Basics of API testing

Introduction to Postman API testing tool covering basics of API, client-server architecture, and importance of API testing in software development.

Key Takeaways

Postman is a useful tool for manual API testing.
Understanding client-server communication is essential for API testing.
API acts as a mediator between client requests and server/database responses.
API testing is crucial to ensure the middle layer works correctly and software quality improves.
Web applications consist of multiple layers including frontend, API layer, and database.

What the video covers

Introduction to Postman as a manual API testing tool and overview of the series.
Explanation of what APIs are and the basics of API testing.
Overview of client-server architecture and how web applications work.
Description of how browsers act as clients sending requests to web servers.
Discussion on request-response communication between client and server.
Role of API as a mediator between client requests and server/database responses.
Importance of API testing in ensuring the middle layer functions correctly.
Different layers in web applications: presentation layer, middle layer (API), and database layer.
Types of software testing including frontend, backend, and API testing.
Encouragement to subscribe and watch further sessions for more advanced topics.

Chapters

What is the role of API in web applications?

API acts as a mediator between the client and server, handling requests from the client and communicating with the server or database to provide responses.

Why is API testing important?

API testing ensures that the middle layer of the application works correctly, which is crucial for the overall quality and functionality of the software.

What are the different layers in a web application?

A web application typically consists of the presentation layer (frontend), the middle layer (API), and the database layer, each playing a distinct role in processing and delivering data.

Full Transcript — Download SRT & Markdown

Speaker A

Hello everyone. From today, we are going to start a new series on Postman API testing tool. Postman is a very good testing tool. Today is our first session for API manual testing. So today, we will start with the basics. If you guys like the video, like the video and subscribe to the channel to support me and watch the video till the end. Let's start today's session.

Speaker A

subscribe the channel to support me and watch the video till the end let's start today's session before discussing API Testing in detail we will focus on the basics of what is API what is API testing What are the types of testing, what is an application, how does a web server work,

Speaker A

Before discussing API testing in detail, we will focus on the basics of what is API, what is API testing, what are the types of testing, what is an application, how does a web server work, what is a client-server, what tools are available in the market, and why we need testing for API testing. Because whenever we develop software, we need to develop software on the basis of customer feedback or market feedback, then we do many types of testing on it to improve the quality of the software, to improve our delivery. We do frontend testing, in which our web testing goes.

Speaker A

we do many types of testing on it, to improve the quality of the software, to improve our delivery, we do frontend testing. In which our web testing goes.

Speaker A

Backend testing, in which database testing comes, and API testing also comes in backend testing. Well, API testing also comes in backend testing only. So today, we are going to discuss API in detail. Before discussing API testing in detail, we will cover the basics first. Let's start with the basics of web applications.

Speaker A

to understand the basics of web applications, the diagram is copied from the net, how it works. Now, in this diagram, we have a desktop system shown here. Yes , it can be a desktop, it can be a desktop, it can be a laptop, because we

Speaker A

To understand the basics of web applications, the diagram is copied from the net, how it works. Now, in this diagram, we have a desktop system shown here. Yes, it can be a desktop, it can be a desktop, it can be a laptop, because we use laptops to access applications, and it can also be mobile. Okay, this is what we showed the system. In the diagram, it can be any of these: desktop, laptop, mobile, can be anything. Now inside desktop, we have a browser. Browser can be any.

Speaker A

chrome browser can be firefox ok can be opera so what happened it became the client it became the client.

Speaker A

Chrome browser, can be Firefox, okay, can be Opera. So what happened? It became the client. It became the client.

Speaker A

we open the browser then in that we enter www.google.com, we enter the url www.google.com ok then we enter like so what happens like we enter If we do, what happens, a request goes, it is showing here, don't speed it up, it

Speaker A

System in which we open the browser and enter the URL. For example, let's say we want to access Google's website. Okay, so what do we do in our laptop or desktop or mobile? We open any browser: Chrome, Firefox, Opera, Internet Explorer, any one.

Speaker A

in the server, but what we do with our client is send a request and how that request goes through the internet. goes through web sir till the voice and then what the web server does based on the request send by the client he responds to us the page from here which is our request here

Speaker A

We open the browser, then in that we enter www.google.com. We enter the URL www.google.com, okay, then we enter like. So what happens? Like we enter. If we do, what happens? A request goes. It is showing here, don't speed it up.

Speaker A

software application is installed in the web server itself Well, it resets in the web server itself, and through the web server, we get the HTML page in response on the client system, okay, so in this way, whenever we send a request to the web application, its page through the internet

Speaker A

It wants a request from laptop or mobile. The web server is fine through the internet, because this page of Google is our client system. It is not installed in me, which is actual software, which is actual software, which is actual software. Do this application, software or web application, it is installed.

Speaker A

software, okay, this is software, so client code, hardware, well, software, so whatever we search in HTML, web application, whatever we search or open on our client, then in that Request and response communication is there, so here we will call it client server communication, what will we call it, client server communication, this is client server architecture,

Speaker A

In the server, but what we do with our client is send a request and how that request goes through the internet. Goes through web server till the voice and then what the web server does based on the request sent by the client, he responds to us the page from here which is our request here.

Speaker A

If it does, here is the request, the response is the request from the client, for the page, whatever page we have opened, we have opened google, then we have opened rediffmail, we have opened any one, we have opened Facebook, it

Speaker A

In his response, we get that HTML page on the display of the client. Okay, so what is happening here? Request and response here communication is happening. Request is being sent from the client to the web server because the actual Google.

Speaker A

missing of API in this now let me tell you this Hello you guys I hope you guys must have understood how the client server communication is happening how we how this web application works now I will tell you next what is the role of API in this where does API come in this whole communication What is

Speaker A

Software application is installed in the web server itself. Well, it resides in the web server itself, and through the web server, we get the HTML page in response on the client system, okay. So in this way, whenever we send a request to the web application, its page through the internet.

Speaker A

It is done for two different types of applications, okay, the definition is understood, now those two applications may be their technology is different, their platform also becomes different, in our two applications and If we understand where it comes in the communication of the web application, then to understand it,

Speaker A

Request comes, you are web server and we get response. In response, we get HTML page on client side, so it is client. It can also be client hardware. Now what is it? Desktop, laptop, mobile, it is all hardware, it is all hardware. It's hardware and it's what is browser, what is this, this is.

Speaker A

any browser will open, then this request will go through the internet, where will it go to the API, because this API is acting as a mediator.

Speaker A

Software, okay, this is software. So client code, hardware, well, software. So whatever we search in HTML, web application, whatever we search or open on our client, then in that request and response communication is there. So here we will call it client-server communication. What will we call it? Client-server communication. This is client-server architecture.

Speaker A

this request to the server. okay so what is this this is our middle layer this is our middle layer this is our front layer presentation layer also we say this is our front end or you can take it as presentation layer

Speaker A

Right, client-server architecture, this way of communication, we call it client-server communication and the architecture that is it is client-server architecture.

Speaker A

if you look in the form of layers this is done our middle, and this is done our presentation layer okay and this is our this is our database Layer where we have all our data it is API in server itself and database in server itself and web server in server itself

Speaker A

If it does, here is the request, the response is the request from the client, for the page, whatever page we have opened, we have opened Google, then we have opened Rediffmail, we have opened any one, we have opened Facebook, it.

Speaker A

, the entire business logic is written near the API, the programming interface programs all the business logic, it is in this middle layer. happens in business logic happens that's all in the middle layer it's the whole program application

Speaker A

Wants the request of the page to the web server now. Actual software resides in web server and from there we get that HTML page in response, okay, on client system. Now where is API in this? Now what is.

Speaker A

add something to the database from the client side, then the entire application program interface does it, okay, whatever data we fetch from the spring, we have to display it on the web on the browser. On the application, it does less

Speaker A

Missing of API in this? Now let me tell you this. Hello you guys, I hope you guys must have understood how the client-server communication is happening, how we, how this web application works. Now I will tell you next what is the role of API in this, where does API come in this whole communication? What is.

Speaker A

do on the front end is called web testing and the testing we do on the API is called API testing on the middle layer. The testing we do is called API Testing, Application Programming Interface Testing and the testing we capture on the database

Speaker A

The full form of application programming interface? Suppose, we have different types of applications and if we want to communicate them with each other, then for that we do API.

Speaker A

which has become our web page. ok now develop presentation so for web page we need scripting language for web page it is html this is scripting language javascript, CSS.

Speaker A

It is done for two different types of applications, okay, the definition is understood. Now those two applications may be their technology is different, their platform also becomes different, in our two applications and if we understand where it comes in the communication of the web application, then to understand it,

Speaker A

extra now see here now here on all three layers If frontend design scripting language is required, for API programming we need programming skills, and for database we need database knowledge. So here, , all there work are done by different teams, different teams do it,

Speaker A

We do the same diagram which we have seen earlier, so there is an API in the middle, in this diagram I copied it from the net. Now look here, now as I told you that this server side is fine, if.

Speaker A

application is, if any request has to be sent to the server, then that Will sell a little bit of API, this is our web page, so whatever request will come from web page, it will go through API till brinjal and whatever response will go through API, it will also go through API to client, here is our client here

Speaker A

Any browser will open, then this request will go through the internet, where will it go to the API, because this API is acting as a mediator.

Speaker A

's do testing, we do API testing here, we don't do web page in that, whatever request we want to send, we directly send it here to Pay API and also we check spawns here, then API testing is done here. is here ok api testing is done directly with api

Speaker A

It is working as a mediator between client and server. Application program interface is acting as an interface between the client and the server, it acts as the mediator. It will go to the API first, the request will go to the API first, then the API will send.

Speaker A

goes then we can do it directly we can also do web page testing we can not do it why is it necessary to do testing then it is necessary to do API testing This is because the communication that is

Speaker A

This request to the server. Okay, so what is this? This is our middle layer. This is our middle layer. This is our front layer, presentation layer also we say. This is our front end or you can take it as presentation layer.

Speaker A

if our middle layer is apl layer if it is not working properly if it is not perfect that's why api testing is very important this is first point now second The point is the second import The main point is that the web application that is being developed by a separate team runs separately, so many times it happens

Speaker A

Like presentation layer which responds. Doing that also through API is happening through API. This is mediator, so this is a middle layer. API is at our middle layer.

Speaker A

testing is done at our API level only. Our 78% testing gets over in API testing because our business logic which is our business logic is not on API layer but business logic is on your API layer so that's why I am testing 78%

Speaker A

If you look in the form of layers, this is done our middle, and this is done our presentation layer, okay, and this is our, this is our database layer where we have all our data. It is API in server itself and database in server itself and web server in server itself.

Speaker A

is not important, that's it. It is not that only API testing is important, it is very important because We can check some functionality only through youth testing, but if we have done our API testing well, then majority of our testing gets completed here

Speaker A

Okay, this is our server side. All three things have come in server side, okay. It works as mediator between client and server. What does the intermediary do between the web server and the database, whatever the request is from the client.

Speaker A

testing of HTML web application. So it takes very little time on time to test the application if our API testing is done well then communication is fine if API is running properly API is perfect then all communication will be fine then there would be

Speaker A

The entire business logic is written near the API. The programming interface programs all the business logic. It is in this middle layer. Happens in business logic happens, that's all in the middle layer. It's the whole program application.

Speaker A

multiple Clients are A B C the multiple computers will be And directly it will be a single database and directly interacting with that database there is no middle layer in between and one way formation which is web communication which is always in 3 tier where we have a

Speaker A

Programming interface is program between two applications. It's program interface API, okay. One application is on our server side between these two that's mediator's extracting whatever data from the web database to send to the application, to send it to the client side or to.

Speaker A

Middle Layer Nahi Hota Directly Jo Clients Who Are We Will Have Multiple Clients Many They Directly Interact With The Database There Is No Mediator In The Middle Okay So I Have Briefly Explained To You People That 18 Tu T And What is city architecture, then web is web communication,

Speaker A

Add something to the database from the client side, then the entire application program interface does it, okay. Whatever data we fetch from the spring, we have to display it on the web, on the browser. On the application, it does less.

Speaker A

i so called representation state transfer which in short we call rest rr old now what is being done in the company it is rest appion both website [music] what is api vs website api's development environment done here set of developers team hai tu devel kar rahi hai

Speaker A

API and if any data from trunted, if we have to add to the database, insert it, then it does less API itself. All the business logic written inside the API is fine. So the testing we do on the front end is called web testing, the testing we.

Speaker A

then we call it web service web services r api only all web services r api all web services r API BUT ALL API ARE NOT WEB SERVICES ALL WEB SERVICES ARE API BUT ALL API NOT WEB SERVICES THIS WE HAVE TO REMEMBER WHEN API IS

Speaker A

Do on the front end is called web testing and the testing we do on the API is called API testing on th

Speaker A

web services ok because it is not necessary that we all our apps our internal It is not necessary that we will put all the apps on the web, it is not necessary that we will put all the onions on the internet, we will

Speaker A

put all the apps on the network, okay, some apps are also our internal, they are not applications, but all web services are API so this is the basic difference between API and web services I hope you guys must have understood that what is the difference between up and web services we need

Speaker A

network but for API we do not need network connection and we Automation testing can also be done automatically, we can do many tours available in the market for manual testing and automation testing, API scheme postman soap, many tours are available in the market, but in this series, postman is

Speaker A

used for manual testing. so in today's session In this article, we have discussed how the application works, what is the client server, what are the apps, why we need API testing, what is the difference between API and web services, what are the tools for API testing,

Speaker A

manual manual testing If you can do automation testing, then I hope you guys must have understood, then today's session is just that, in the next session with new topics, if you liked the video, then like the video more than the channel. Share subscribe channel and press bell icon thanks for watching

Topics:PostmanAPI testingclient-server architectureweb applicationsmanual testingsoftware testingAPI rolefrontend testingbackend testingAPI mediator

Get More with the SozAI App

Transcribe recordings, audio files, and YouTube videos — with AI summaries and speaker detection. 30 minutes free.

App Store Google Play

Or transcribe another YouTube video here →

Free tools: TXT to SRT · SRT Validator · Merge SRT · Subtitle to Text · All tools