KEMBAR78
Session-5 Tosca API Testing | PDF
Scribd
Upload
45 views4 pages

Session-5 Tosca API Testing

API testing evaluates application programming interfaces for functionality, reliability, performance, and security, typically at the message layer due to the absence of a GUI. The two main API technologies discussed are SOAP, a longstanding protocol, and REST, which offers a simpler alternative. The document outlines common HTTP status codes and provides a step-by-step execution process for testing APIs.

Uploaded by

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

Session-5 Tosca API Testing

API testing evaluates application programming interfaces for functionality, reliability, performance, and security, typically at the message layer due to the absence of a GUI. The two main API technologies discussed are SOAP, a longstanding protocol, and REST, which offers a simpler alternative. The document outlines common HTTP status codes and provides a step-by-step execution process for testing APIs.

Uploaded by

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

About API:

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. Since APIs lack a GUI, API testing is performed at the message layer.
Two API Technologies:

- SOAP (Simple Object Access Protocol) is a standards-based web services


access protocol that has been around for a long time. Originally developed
by Microsoft, SOAP isn’t as simple as the acronym would suggest.

- REST (Representational State Transfer) is another standard, made in


response to SOAP’s shortcomings. It seeks to fix the problems with SOAP
and provide a simpler method of accessing web services.

Test Site’s:
https://reqres.in/
https://petstore.swagger.io/
Mainly used Request Operation’s:
HTTP Status Codes in the REST API
 200 OK. The 200 OK status code indicates the request succeeded. ...
 303 See Other. The 303 See Other status code indicates that you are being
redirected to another resource via the "Location" response header. ...
 400 Bad request.
 404 Resource not found.
 500 Internal server error.

Execution:
1. Select any option URI/ File/ Through creating the Folder manually & create
message for the Request.
2. Now click on Run for the Each Request & Verify the Status codes.
3. Post that imports to the Test Cases
4. Now Create action modes for the status code’s & Add buffer to the ID.
5. Create Execution folder & execute all the operations at a time.

You might also like