An API provides much of the functional capabilities in complex software systems.
Most customers are accustomed to interacting with a graphical user interface on the computer. But, many do not realize that much of the functionality of a program comes from APIs in the operating system or the program’s dynamic-link libraries (DLL).
When the business logic or core functionality is exposed via an API call and you want to find functional bugs sooner, then API testing can provide additional value in your overall test strategy. API testing can start even before the user interface is complete, so functional capabilities can be tested while designers are hashing out the “look and feel.” While API testing will not replace testing through the user interface, it can augment your test strategy and provide a solid foundation of automated tests that increase your confidence in the functional quality of your product.
At EuroSTAR 2013 BJ Rollison gave an excellent presentation on API testing that is well worth watching.
- What is API Testing?
- Why do API testing?
- The difference between Unit and API tests
- How to approach API testing
- Types of bugs testing will find