The slides gives you the quick, simple, understandable information on API testing. It touch all aspects of testing done under API Testing. he

1. A Quick glance
By
Dhanu

2.  Definition
 API Testing is a type of software testing that involves testing application
programming interfaces (APIs) directly and as part of integration testing to
determine if they meet expectations for functionality, reliability, performance,
and security
 Advantages
 Test for Core Functionality
 Time Effective
 Language-Independent
 Cost Effective / Reduces Testing Cost

4.  Concept
 Representational State Transfer (REST) is an architectural style that
specifies constraints, such as the uniform interface, that if applied to a web
service induce desirable properties, such as performance, scalability, and
modifiability, that enable services to work best on the Web
 Resource identification through URI: A RESTful web service exposes a set
of resources that identify the targets of the interaction with its clients.
Resources are identified by URIs, which provide a global addressing space
for resource and service discovery.
 Uniform interface: Resources are manipulated using a fixed set of four
create, read, update, delete operations: PUT, GET, POST, and DELETE.
PUT creates a new resource, which can be then deleted by using DELETE.
GET retrieves the current state of a resource in some representation. POST
transfers a new state onto a resource.
 Self-descriptive messages: Resources are decoupled from their
representation so that their content can be accessed in a variety of formats,
such as HTML, XML, plain text, PDF, JPEG, JSON, and others. Metadata
about the resource is available and used, for example, to control caching,
detect transmission errors, negotiate the appropriate representation format,
and perform authentication or access control.

5.  Resources – Uniform Resource locator
 Methods
 HTTP Result code
 Data schema

6.  GET- The GET method is used to extract information from the given
server using a given URI. While using GET request, it should only
extract data and should have no other effect on the data.
 POST- A POST request is used to create new entity. It can also be used
to send data to the server, for example, customer information, file
upload, etc. using HTML forms.
 PUT- Create a new entity or update an existing one.
 DELETE- Removes all current representations of the target resource
given by a URI.

8.  Initial Setup of API Testing
 Updating the Schema of API Testing
 Testing Parameter Combinations
 Sequencing the API Calls
 Validating Parameters
 Tracking System Integration

9.  Functionality Bugs
 Reliability Bugs
 Performance Bugs
 Security Bugs

10.  Customer Portfolio- Feature, where we give the customer ID and
customer information along with the encrypted ID generated, while
defines whether information should displayed if all business rules
satisfies
 Input and Output – Customer ID as input and out as customer
information and customer key
 Cross Verification – It is done through database table, querying
database for customer information for given customer ID

11.  https://www.apicasystems.com/blog/types-
bugs-api-testing-find/
 Wikipedia