Input Injection: It is the act of simulating user input, in several ways you can simulate user input.
The key area to be considered when writing API documents are:
The main challenges in API testing is:
The tools used for various API testing are:
While testing Unit and API testing, both target source code, if an API method is using code based on .NET then the tool which is supporting should have .NET
Automation tools for API testing can be used are:
API (Application Programming Interface) specifies how some software components should interact with other, in other words it’s a set of functions and procedures that allows the creation of applications which access the features or data of an application or operating system. Testing of these functions is known as API testing.
It is a set of functions to which the developers performs requests and receive responses. In REST API interaction is made via HTTP protocol
REST – stands for Representational State Trfer, it is quickly becoming defacto standard for API creation.
Description: Small description about what a function does
Syntax: Syntax about the parameter of the code, the sequence in which they occur, required and optional elements etc.
Parameters: Functions parameters
Error Messages: Syntax of error messages
Example Code: Small snippet of code
Related Links: Related functions
Popular tools used for API documentations are JavaDoc (for Java code ) Doxygen (for .Net code)
Runscope is a web application that provides backend services and easy to use interface for testing APIs.
The types of Bugs, API will find:
API testing steps:
API framework is self-explanatory. Values for test run and for holding the configurable parts, config file is used. Automated test cases must represent in “ parse-table” format within config file. When testing API, it is not necessary to test each API so the config file have some section whose all API are activated for that specific run.
TestApi is a library of utility and test APIs that enables testers and developers to create testing tools and automated tests for .NET and Win32 application. It provides a set of common test building blocks, types, data-structure and algorithms.
UI ( User Interface) refers to testing graphical interface such as how user interacts with the applications, testing application elements like fonts, images, layouts etc. UI testing basically focuses on look and feel of an application.
While, API enables communication between two separate software systems. A software system implementing an API contains functions or sub-routines that can be executed by another software system.
API Builder is a PLSQL program consists of four SQL files:
SOAP-stands for Simple Object Access Control, and it is an XML based protocol for exchanging information between computers.
The principle for API test design are:
Setup : Create objects, start services, initialize data etc
Execution: Steps to exercise API or scenario, also logging
Verification: Oracles to evaluate execution outcome
Reporting: Pass, failed or blocked
Clean up: Pre-test state