API/Web service Testing

What is An API?

An API (Application Programming Interface) is a collection of software functions and procedures, called API calls that can be executed by other software applications; it defines how software components

interact with each other.

What is a Web Service?

Web Services is the mechanism or the medium of communication through which two applications / machines will exchange the data irrespective of their underline architecture and the technology.

API Testing is done to make sure that the basic functional units of the software system works perfectly well. API testing is specifically the testing of API functions and it testing mainly concentrates on the business logic layer of software architecture and not on the look and feel of the application.

API testing is designed to consider the ‘full’ functionality of the system, as it will be used by the end user.

API testing requires the testing tool to interact with the API there are several tools for testing API some of which includes:

  • Fiddler, Webinject, Junit, XMLUNIT, HttpUnit, ANT

What Sunbonn believes?

We at sunbonn believe that each and every functional unit of application should work perfectly well that’s why we implement API testing because by implementing API testing we can identify the smaller errors and it helps us in evaluating the strength of the build and allows the faster release with the improved test coverage. We also believe that the cost of bug fixing is drastically less in API level as compare to when those functionality bugs are found by user from application user interface.

Our approach to test any product that contains an API is:

  • Understand that API Testing is a testing activity that requires some coding and is usually beyond the scope of what developers are expected to do.
  • Traditional testing techniques such as equivalence classes and boundary analysis are also applicable to API Testing
  • It is almost impossible to test all possible scenarios that are possible to use with your API. Hence, one should focus on the most likely scenarios, and should also apply techniques like Forced Error Testing using different data types and size to maximize the test coverage

Contact Us

214 380 5475


Sign up Now

for receiving our monthly newsletter