API Testing Interview Questions and Answer 2020

  • By Revati Raspayle
  • December 27, 2019
  • Software Testing
API Testing Interview Questions and Answer 2020

Interview Questions and Answer | API Testing

Q1)  What are the different types of tools used for API testing?

Ans-  The tools used for  API testing are

  • Parasoft SOAtest
  • SoapUI Pro
  • PostMan
  • Rest Assured
  • Alertsite API monitoring

For Free Demo classes Call: 8237077325
Registration Link: Click Here!

Q 2) What is API testing?

Ans-   API stands for Application Programming Interface , where it specifies how some software components should interact with other software, in other words it is a set of functions and procedures that allows the creation of applications or software which access the features or data of an application.  Testing of these functions is known as API (Application Programming Interface) testing.

Q3) What are the common tests performed on API is?

Ans-  The common tests performed on API’s

  • Checking of the API whether it is updating any data structure
  • Verify whether the API does not return anything
  • Based on input conditions, returned values from the API is are checked
  • Checking/Verification of the API whether it triggers some other event or calls another API.

Q4) Mention the difference between API testing and UI level testing ?

Ans-  UI stands User Interface that refers to do testing graphical user interface(GUI) part such as how end user interacts with the applications, testing application elements like fonts, color, images, layouts etc. UI testing basically focuses on feel and look of an application.

While, API enables communication between two different software systems. A software system implementing an API contains functions that can be executed by another software system.

Q5) Explain what is REST API?

Ans-  It is a set of functions or instructions to which the developers performs requests and receive responses. In REST API interaction is made via HTTP protocol server.

REST stands for Representational State Transfer where t is quickly becoming defacto standard for API creation.

Q6) Difference API and Unit Testing?

Ans-

API testing UNIT testing
·        API is owned by QA team

 

·        Unit testing is owned only by development team

 

·        API is mostly black box testing (BBT) ·        Unit testing is white box testing (WBT)

 

·        Full functionality of the system is considered in API testing as it will be used by the end-user( developers who will use your API ) ·        Unit testing is done to verify whether each unit is expected to be performs as expected or not

 

·        API test are often run after the build or module is ready and clients do not have access to the source code ·        For each of their module the developers are expected to build unit test cases for each of their code modules and have to ensure that each module should pass unit test before the code is included in a build.

 

 

Q7) How to test API is ?

Ans-  To test the API’s you should follow the below steps

  • Select test suite in which you want to add the API test case
  • Choose test development mode
  • Configure application control parameters
  • Configure test conditions
  • Configure method validation
  • Execute API test
  • View test reports
  • Filter API test cases
  • Sequence API test cases

For Free Demo classes Call: 8237077325
Registration Link: Click Here!

Q8) What are the important challenges of API testing?

Ans-  The main challenges in API testing is

  • Parameter Selection
  • Parameter Combination
  • Call sequencing

Q9) What is API testing with runscope ?

Ans-  Runscope is one of the web application that provides backend services and easy to use interface for testing APIs.

Q10) what are the principles of API test design?

Ans-  The principle for API test design are

  • Setup : Create objects, start api services, initialize data etc
  • Execution: Steps to work on API or scenario, also logging
  • Verification: Oracles to evaluate execution outcome
  • Reporting: Pass, failed or blocked
  • Clean up: Pre-test state

Q11) What are the types of Bugs will found while doing API testing?

Ans-  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

Q12) What are the tools available for API test automation?

Ans-  If an API method is using code which is based on .NET then the tool which is supporting should have .NET

following are the list Automation tools for API testing:-

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

Q13) What are the common protocols used while testing in API tesing ?

Ans-

  • HTTP
  • JMS
  • REST
  • SOAP
  • UDDI

JIRA (Bug tracking tool) Interview Questions & Answers

Q1) What is JIRA?

Ans-  JIRA is an  bug tracking product or a software tool developed by Atlassian company. It commonly used for issue tracking, project management, and bug tracking; it is completely based on these three aspects. It is widely used in software development and software testing.

Q2) What is a workflow JIRA?

Ans-

  • WIP ( Work In Progress):-Workflow is defined of the bug/issue through various stages during its life-cycle
  • Created/Open
  • Completed/Closed

Q3) What kind of features as an issue in Atlassian JIRA?

Ans-   In JIRA, an issue can be like : –

  • Software bug
  • The project task
  • A help-desk ticket
  • The leave request form

Q4) Why use JIRA software?

Ans-  The reason behind using JIRA is

  • Upfront and fair licensing policy
  • Features that is not available elsewhere
  • Get the latest update on the progress of projects
  • It runs any environment and recognized with many famous companies
  • Easily extensible and customizable

Q5) Does it possible to access JIRA cloud site via a mobile device?

Ans-  Yes, it’s possible to access JIRA cloud site via a mobile device. You can use the URL of the JIRA cloud site in your mobile web browser.

Q6) Can you disable JIRA mobile for the website?

Ans-  You can disable JIRA mobile for the site so,  that employee can be unable to operate the desktop view of JIRA on their mobile device.  JIRA mobile comes as a system add-on and it  can be disabled at any time.

Q7) Explain labeling and linking issue in JIRA

Ans-

  • Labeling Issue:It enables you to classified an issue in a very informal way than assigning it to a component or version. You can then search issues according to the label.
  • Linking Issue: This feature enables you to link an association between two issues on either on same or different JIRA servers.

Q8)  Name the types of reports generated in JIRA

Ans-  JIRA offer  different reports that show statistics for projects, there versions or other fields within issues.  Various reports included with JIRA are follows:-

  • Average Age Report
  • Pie Chart Report
  • Resolution Time Report
  • Recently Created Issues Report
  • Resolved vs. Created Issues Report
  • Single Level Group by Report
  • Time Tracking Report
  • User Workload Report
  • Workload Pie Chart Report, etc.

For Free Demo classes Call: 8237077325
Registration Link: Click Here!

Q9) What is Cloning an Issue?

Ans-  Cloning as issue allows you to create a duplicate issue of the original issue so that many employees can work on a single issue within a single project.   A clone issue holds following the information

  • Summary
  • Description
  • Assignee
  • Environment
  • Priority
  • Issue Type
  • Security
  • Reporter
  • Components, etc.

Q10) What are the things which cannot included in cloned issue in JIRA?

Ans-

  • Time tracking
  • Issue History
  • Comments

Q11) How is security setting helpful in JIRA?

Ans-  JIRA  security setting restricts access to the issue to only those person who is allowed to work on the issue or a member of the chosen security level. The security level of an issue can be set either when the issue or bug is created or when the issue is being edited/updated.

Q12) How can you share an Bug with other users in JIRA?

Ans-  You can email an issue or bug by using the share option in JIRA. You can also email to other JIRA users a link to the issue by sharing the issue with them or by mentioning them in an issue’s in Comment field.

Q13) How you can modify multiple bulk issues?

Ans-   To modify multiple bulk issues, you can select the Bulk Change option from the “Tools” menu of the navigator.  All the issues on the current page can be selected for the bulk action.  The following list details the available bulk operations

  • Workflow Transition
  • Delete
  • Move
  • Edit

Q14) What does an issue change history include?

Ans-  Issue change history includes

  • Deletion of a comment
  • Deletion of a work log
  • Creation or removal of an issue link
  • Attachment of a file
  • Changes to an issue field

Q15) What are the common  the popular add-ons for JIRA?

Ans-   Some popular add-ons for JIRA are :-

  • Suites utilities for JIRA
  • ScriptRunner for JIRA
  • Zephyr for JIRA – Test Management
  • JIRA Toolkit Plugin
  • Atlassian REST API Browser
  • Portfolio for JIRA
  • JIRA Misc Workflow Extensions
  • Tempo Timesheets for JIRA
  • JIRA Charting Plugin

Q16) Give some useful tips on JIRA Workflow

Ans-

  • As such Status can be assigned global objects in JIRA. Changing the name of the status on one workflow will change the status on all workflows that use that status
  • Hover over status to see the relevant transition labels
  • One can’t clone transitions in the workflow designer
  • In the workflow designer of Jira, one cannot create annotations
  • In JIRA , Directly you cannot set the issue editable property.

 

Q17)  State the difference between Bugzilla and JIRA?

Ans-

Bugzilla JIRA
·          Bugzilla  is an Open Source ·          JIRA is a commercial tool
·           Bugzilla is little bit complicated for few due to grouping users and granting permissions ·           JIRA would be more convenient than Bugzilla.
·          Bugzilla allows you to show or hide whole custom field/ value based on the value of some other field ·          JIRA enables conditional configuration based only on Type fields and Project.
·          Bugzilla is has a powerful advanced search option for issue tracking ·          JIRA lacks advance-level search options. JIRA has a flexible (JIRA Query Language) language.
·           Bugzilla allows users to select the initial status of a new issue. ·          JIRA enables you to define multiple workflows which are applied based on the issue is Project and Type.
·          Bugzilla has only one link type: Blocks or depends and a Bug ID custom field ·          JIRA has configurable link types with user-defined semantics. JIRA enables to link an issue to any other entity which outside JIRA.

 

Author:

Raspayle, Revati | SevenMentor Pvt Ltd.

For Free Demo classes Call: 8237077325
Registration Link: Click Here!

Call the Trainer and Book your free demo Class for now!!!

call icon

© Copyright 2019 | Sevenmentor Pvt Ltd.

Submit Comment

Your email address will not be published. Required fields are marked *

*
*