API (Application Programming Interface) <\/strong><\/em>is a software intermediary that enables two applications to communicate with each other. HTTP-based API is often called a Web API since they are used to access Web Applications which are deployed to Servers accessible over the Internet or network. Applications that are accessed via HTTP APIs are often called Web Services.<\/p>\n Mobile Applications often use Web Services and REST APIs to communicate with servers to implement their functionality. The Mobile Application processes the message returned from the Web Service and displays it to the User in the application GUI. So again, the user is unaware that HTTP requests are being made or of the format of the requests and responses.<\/p>\n ___________________________________________________________________________<\/p>\n API Testing<\/b>– It is a kind of software testing to determines and check if the developed APIs meet expectations regarding the functionality, reliability, performance, and security of the application or not<\/p>\n Common protocols that are testing in API testing are<\/strong> -HTTP, JMS, REST, SOAP, UDDI<\/p>\n Types-<\/b>Validation Testing, Functional Testing, UI testing, Load testing, Runtime\/ Error Detection, Security testing, Penetration testing, Fuzz testin, Interoperability testing<\/p>\n E<\/b>xample of API Testing:<\/b><\/p>\n Twitter<\/b>: The API for Twitter is usually in two categories, one for accessing data and the other for interacting with the Twitter search.<\/p>\n YouTube<\/b>: This API used for YouTube includes various functionalities including videos, live streaming, player, etc.<\/p>\n Google Maps AP<\/b>I: These are designed mainly for mobile and desktop use with the help of a flash interface and JavaScript.<\/p>\n Amazon Advertising API<\/b>: Amazon is known for their products and thus their advertising API accesses their product to discover their functionality and thus advertise accordingly<\/p>\n ADVANTAGES<\/b> of API Testing: <\/strong><\/p>\n <\/strong>Compatibility and easy integration with GUI<\/b>: Simple integration would allow new user accounts to be created within the application before a GUI test started.<\/p>\n Language-Independent<\/b>: In API testing, data is exchanged using XML or JSON. These transfer modes are completely language-independent that allows users to select any coding language while adopting automation testing services for the project.<\/p>\n Time Effective<\/b>: In comparison to functional GUI testing API testing usually is less time-consuming. The web elements in GUI testing must be polled, which makes the testing process slower. Particularly, API test automation requires less code so it can provide better and faster test coverage compared to GUI test automation.<\/p>\n Test for Core Functionality<\/b>: API testing provides the ability to access to the application without a user interface. The core and code-level of functionalities of the application will be tested and evaluated early before the GUI tests. This helps in detecting the minor issues which can become bigger during the GUI testing<\/p>\n ______________________________________________________________________________<\/p>\n Main differences are given below:<\/strong>a) All web services are APIs but not all APIs are web services.<\/p>\n b) A web service uses only three styles of use: SOAP, REST, and XML-RPC for communication whereas API may be exposed to in multiple ways.<\/p>\n c) A web service always needs a network to operate while APIs don\u2019t need a network for operation.<\/p>\n d) Web services might not contain all the specifications and cannot perform all the tasks that APIs would perform.<\/p>\n ______________________________________________________________________________<\/p>\n API enables the communication between two separate software systems. A software system implementing an API contains functions or subroutines that can be executed by another software system.<\/p>\n On the other hand, UI ( User Interface) testing refers to testing graphical interface such as how users interact with the applications, testing application elements like fonts, images, layouts, etc. UI testing basically focuses on the look and feel of an application.______________________________________________________________________________<\/p>\n Basically, there are five most important principles of an API test design:<\/p>\n Setup<\/b>: Create objects, start services, initialize data, etc<\/p>\n Execution:<\/b> Steps to apply API or the scenario, including logging<\/p>\n Verification<\/b>: Oracles to evaluate the result of the execution<\/p>\n Reporting<\/b>: Pass, failed or blocked<\/p>\n Clean up<\/b>: Pre-test state<\/p>\n ______________________________________________________________________________<\/p>\n a) Create the suite to add the API test case<\/p>\n b) Create the test development mode<\/p>\n c) Demand the development of test cases for the required API methods<\/p>\n d) Configure the control parameters of the application and then test conditions<\/p>\n e) Configure method validation<\/p>\n f) Arrange all API test cases<\/p>\n g) Execute the API test<\/p>\n h) Check test reports<\/p>\n ______________________________________________________________________________<\/p>\n a) Accuracy of data<\/p>\n b) Non-functional testing like performance and security testing<\/p>\n c) Implementation of response timeout<\/p>\n d) Schema validation<\/p>\n f) HTTP status codes<\/p>\n g) Data type, validations, order, and completeness<\/p>\n h) Authorization checks<\/p>\n I) Error codes in case API returns<\/p>\n ______________________________________________________________________________<\/p>\n A few common tools are Katalon Studio, Postman, SoapUi Pro, Apigee, automated API testing using REST Assured and CURL etc.<\/p>\n ______________________________________________________________________________<\/p>\n a) Missing or duplicate functionality<\/p>\n b) Stress<\/p>\n c) Reliability<\/p>\n d) Security<\/p>\n e) Performance<\/p>\n f) Unused flags<\/p>\n g) Not implemented errors<\/p>\n h) Inconsistent error handling<\/p>\n I) Improper errors<\/p>\n j) Fails to handle error conditions gracefully<\/p>\n k) Multi-threading issues<\/p>\n ______________________________________________________________________________<\/p>\n API is owned by QA team where as Unit testing is owned by the development team<\/p>\n API is mostly black box testing where as Unit testing is white box testing<\/p>\n Full functionality of the system is considered in API testing as it will be used by the end-user (external developers who will use your API )where as Unit testing is done to verify whether each unit in isolation performs as expected or not<\/p>\n API test are often run after the build is ready and authors do not have access to the source code where as For each of their module, the developers are expected to build unit tests for each of their code modules and have to ensure that each module pass unit test before the code is included in a build.<\/p>\n ______________________________________________________________________________<\/p>\n 1) Parameter Selection<\/p>\n 2) Parameter Combination<\/p>\n 3) Call sequencing<\/p>\n ______________________________________________________________________________<\/p>\n There are several available API documentation templates help to make the entire process simple and straightforward.<\/p>\n ______________________________________________________________________________<\/p>\n Hypertext Transfer Protocol is a way of sending messages to software on another computer over the internet or over a network.<\/p>\n An HTTP request is sent to a specific URL and consists of:<\/strong><\/p>\n A) A VERB specifying the type of request e.g. GET, POST, PUT, DELETE<\/p>\n B) A set of HTTP Headers. The headers specify information such as the type of browser, type of content in the message, and what type of response is accepted in return.<\/p>\n C) A body, or payload in the request, representing the information sent to, or from, the Web Application. Not all HTTP messages can have payloads: POST and PUT can have payloads, GET and DELETE do not.<\/p>\n ______________________________________________________________________________<\/p>\n URL is a Uniform Resource Locator and is the address we use to access websites and web applications. When working with APIs you will often see this referred to as a URI (Uniform Resource Identifier). We can think of a URI as the generic name for a URL. When we have to call an HTTP API we need the URL for the endpoint we want to call Example-<\/p>\n https:\/\/www.thetravel.com\/10-best-indian-foods\/<\/a><\/p>\n This is the locator that says \u201cI want to call the \u201c10 best indian foods\u201d resource located at \u201cthetravel.com\u201d using the http protocol\u201d.<\/p>\n The above URL can be broken down into the form:<\/b><\/p>\n scheme:\/\/host\/resource<\/strong><\/p>\n \u2022 scheme<\/strong>-HTTP<\/p>\n \u2022 host<\/strong>-thetravel.com<\/p>\n \u2022 resource<\/strong>-10-best-indian-foods<\/p>\n A larger form for a URL is:<\/b><\/p>\n scheme:\/\/host\/resource?query#fragment<\/p>\n The query is a way of passing parameters in the URL to the endpoint e.g. Google uses query parameters to define the search term and the page:<\/p>\n https:\/\/www.google.co.uk\/?q=test&start=10#q=test<\/a><\/p>\n ______________________________________________________________________________<\/p>\n A web browser will usually make GET requests<\/strong> and POST requests.<\/strong><\/p>\n GET <\/strong>requests to ask to read information from the server e.g. clicking on a link.<\/p>\n POST <\/strong>requests supply information to the server e.g. submitting a form.<\/p>\n GET <\/strong>requests do not have a body, and just consist of the Verb, URL, and the Headers.<\/p>\n POST <\/strong>requests can have a payload body.<\/p>\n When working with a Web Application or HTTP API the typical HTTP Verbs used are:<\/strong><\/em><\/p>\n GET<\/strong>, to read information.<\/p>\n POST<\/strong>, to create information.<\/p>\n PUT<\/strong>, to amend or create information.<\/p>\n DELETE<\/strong>, to delete information.<\/p>\n ______________________________________________________________________________<\/p>\n2. Define API TESTING with its types ,examples and some common advantages?<\/h3>\n
3. What are the main differences between API and Web Service?<\/h3>\n
4. What are the differences between API Testing and UI Testing?<\/h3>\n
5. What are the principles of an API test design?<\/h3>\n
6. What is the procedure to perform API testing?<\/h3>\n
7. What must be checked when performing API testing?<\/h3>\n
8. What are tools could be used for API testing?<\/h3>\n
9. What are the types of Bugs API testing can find?<\/h3>\n
10. Difference API and Unit Testing?<\/h3>\n
11. What are the main challenges of API testing?<\/h3>\n
12. What are API documentation templates that are commonly used?<\/h3>\n
\n
13. Explain what is an HTTP request?<\/h3>\n
14. What is a URL?<\/h3>\n
15. Describe what are HTTP verbs?<\/h3>\n
Course Alert<\/span><\/em>If you are interested in learning API testing, check out some of the popular courses on Rest Assured, SoapUI, Python API testing below:<\/h5>\n
\n
A Quick Note<\/strong><\/em><\/h4>\n