Scribd
Upload
5 views2 pages

API Testing

The document outlines the use of Postman as a manual API testing tool and Rest Assured for automation, detailing the architecture of web applications and the role of APIs in connecting the database and presentation layers. It emphasizes that API testing accounts for 80% of the testing process, with the remaining 20% focused on UI testing, and explains various HTTP request methods. Additionally, it describes the workspace in Postman for organizing collections of requests and the importance of validating response payloads.

Uploaded by

Hase Eb
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
5 views2 pages

API Testing

The document outlines the use of Postman as a manual API testing tool and Rest Assured for automation, detailing the architecture of web applications and the role of APIs in connecting the database and presentation layers. It emphasizes that API testing accounts for 80% of the testing process, with the remaining 20% focused on UI testing, and explains various HTTP request methods. Additionally, it describes the workspace in Postman for organizing collections of requests and the importance of validating response payloads.

Uploaded by

Hase Eb
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

API through Postman

 manual api tool= postman

 automation api tool=rest assured

 web testing comes undr frnot end testing while Api + DB testing comes backed testing

 client is a machine where we can access the application

 server where the application installed

 client is always not browser but it may be a mobile in which difrnt apps we use

 where exactly search pages installed called seever

 web app follows 3 tier architure

 1 tier architure= in same computer save the file and no need of internet

 2 tier architure= a banking aplication have their own internal db and thier staff(i.e multiple
clients) access the db) , differnt clients will access the same db and in 2 tire db present in
difrnt machine not on the same machine

 Api act as an imidiater between db and presentation layer

 responsibility of API layer is to fetch the data from db(backend) and display on front end

 front end layer-> web testing

 middle layer-> API testing

 backend layer-> db testing

 first develop= db then api then web

 if API testing perform then 80% testing is complete only 20% is remaning for ui testing

 API = functional testing

 front end testing= GUI testing

 soap= xml but rest api support= xml , json, text

 when api is placed on the internet then it is called web service

 All web services are APIs but all apis are not web services bcz for api not net require

 api take some requst frm use and give respons and make within company
 once the API is production and make it to use for public then which is called web services

Workspace: Area where we maintain files and saved

workspace-create wokspace,rename and delete

Create collection: Inside workspace we can create 'N' no of collections because sometimes you have
different types of request and we can grop them into folders. contains number of foders and http
request.

we can create the collection , delete, run and rename.

we can create any no of collection under workspace.

HTTP request:

Get--------------> retrive the resource from database.

Post-------------->create resources on db

Put--------------> update esisting resources on DB.

Patch--------------> update partial details of the resources.

Delete--------------> existing data from database

Request payload is nothing the data which we request through the URL.

Always do validations on the response payload.

Created by Khadija Tabassum

You might also like