Explore topic-wise InterviewSolutions in Current Affairs.

• HTTP
• JMS
• REST
• SOAP
• UDDI

API testing steps:

• Select the test case that has to be fulfilled
• For API CALL develop a test case
• To MEET the test case configure the API parameters
• Determine how will you VALIDATE a successful test
• Using programming language like PHP or .NET execute the API call
• Allow the API call to return the data to validate.

API testing steps:

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:

• NUnit for .NET
• JUnit for Java
• HP UFT
• Soap UI

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:

The types of Bugs, API will find:

• Missing or duplicate functionality
• Fails to handle error conditions gracefully
• Stress
• Reliability
• SECURITY
• Unused flags
• Not IMPLEMENTED errors
• INCONSISTENT error HANDLING
• PERFORMANCE
• Multi-threading issues
• Improper errors

The types of Bugs, API will find:

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

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

RUNSCOPE is a web APPLICATION that provides backend services and EASY to USE interface for testing APIs.

Runscope is a web application that provides backend services and easy to use interface for testing APIs.

The main challenges in API testing is:

• PARAMETER SELECTION
• Parameter COMBINATION
• Call SEQUENCING

The main challenges in API testing is:

INPUT Injection: It is the ACT of simulating user input, in several ways you can simulate user input.

• Direct Method INVOCATION
• Invocation USING an accessibility interface
• Simulation using low-level input
• Simulation using a device driver
• Simulation using a robot

Input Injection: It is the act of simulating user input, in several ways you can simulate user input.

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.

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.

API BUILDER is a PLSQL program consists of four SQL files:

• For setting API parameters and starting the process one FILE is responsible
• Two files are created for TEMPORARY tables and Master PACKAGE to create the outputted code
• Fourth file creates “spooled” output of the code into a file called “output_script_.sql”.

API Builder is a PLSQL program consists of four SQL files:

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.

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.

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)

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)

The key area to be CONSIDERED when WRITING API documents are:

• Source of the content
• Document PLAN or sketch
• DELIVERY layout
• Information required for each function in the document
• Automatic document creation programs

The key area to be considered when writing API documents are:

To test the API’s you should follow the following steps:

1. Select the suite in which you want to ADD the API test case
2. Choose test development mode
3. Develop test CASES for the desired API methods
4. CONFIGURE application control parameters
5. Configure test CONDITIONS
6. Configure METHOD validation
7. Execute API test
8. View test reports
9. Filter API test cases
10. Sequence API test cases

To test the API’s you should follow the following steps:

API TESTING:

• API is owned by QA team
• API is mostly black box testing
• 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 )
• API test are often run after the build is ready and authors do not have access to the source code. 

UNIT testing:

• Unit testing is owned by development team 
• Unit testing is white box testing
• Unit testing is done to verify whether each unit in isolation performs as expected or not
• 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.

API testing:

UNIT 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 Transfer, it is quickly BECOMING DEFACTO standard for API creation.

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 Transfer, it is quickly becoming defacto standard for API creation.

SOAP-stands for SIMPLE Object Access CONTROL, and it is an XML based protocol for EXCHANGING INFORMATION between computers.

SOAP-stands for Simple Object Access Control, and it is an XML based protocol for exchanging information between computers.

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.

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.

The common tests performed on API’s:

• Verification of the API whether it is updating any data STRUCTURE
• Verify if the API does not return anything
• Based on INPUT conditions, returned values from the API’s are CHECKED.
• Verification of the API whether it TRIGGERS some other event or calls another API.

The common tests performed on API’s:

The tools used for various API TESTING are:

• SOAPUI Pro
• LoadUI Pro
• Alertsite API MONITORING

The tools used for various API testing 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.

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.