Skip to main content

API Testing

API is the communication and data exchange system between the different software. API defines that how one software interact with the another software. A Software have many function and when these functions are called from another software then we call it API. API stand for Application Programming Interface.
Now we come on the topic of what is the API Testing. Before understanding the API Testing you need to to understand the Software Architecture.
There are three layers in any Software Architecture

  • Presentation Layer: This is the User Interface Layer. This layer provide the translation of task and provide in a mode which can be understandable by user.
  • Logic Layer: This layer coordinate the application, process command, make logical decisions and perform calculations. It also move the data between 2 surrounding layers. 
  • Database Layer: Here is information is stored and retrieve from database or file system. This information first passed to the Logic layer then visible to the users in the Presentation Layer.
API Testing in concentrate over the Logic Layer and not over the Presentation layer so API Testing is differ from the GUI Testing. In API Testing you need a software to send call to API so here you need to Testing Tools to drive API or you should write down his/her own code to Test the API. Now you know that API Testing the White Box Testing. 



Comments

Popular posts from this blog

What is API?

In general way, API (Application Programming Interface) is the intermediate software which is useful for two applications to communicate. API is the tool which is used for interaction of two applications. If developer developing any software which have multiple blocks (Modules) than developer use APIs to put them together.

Ad-Hoc Testing

Ad-Hoc Testing is the testing type which is performed without any proper procedure and without any Requirement Specification. Ad-Hoc testing is totally informal testing which have intension to break the application as early as possible and found important defect early.  In Ad-hoc testing tester do not have any test cases so only the users who have very high knowledge regarding the application only they can perform Ad-Hoc Testing.

Smoke Testing

In Smoke Testing, Testing team check the key feature or key bugs of the software. Smoke testing ensure that critical functionality of the software is working fine.If key features are not working then it is no needed to test the overall functionality because it is just waste of time. In Smoke Testing, test team check the basic feature of the software and if basic feature is not working it means software is broken very badly and further testing is unnecessary. If Smoke Testing failed then it is declared that build is unstable and revert back to developer team until smoke test is pass.