{"componentChunkName":"component---src-pages-author-author-yaml-id-js","path":"/author/surendranath-reddy-birudala/","result":{"data":{"allMarkdownRemark":{"edges":[{"node":{"id":"fa532753-4741-55d8-b856-b8992502bc49","html":"

Until the modifications are introduced to production, smart companies take advantage of API testing and so do you. In both staging and production environments, API's must be checked to ensure that the software framework meets the specifications.

\n

Let's discuss how, through how your team approaches your research plan, your team can get the benefits of API testing.

\n

What is API Testing?\nApplication Programming Interface is often called as API. An API is a set of methods and procedures that developers \"open up\" to other programmers to have their applications communicate and interact with other applications. Once an API is built, it is necessary to test the interface to provide truly secure, reliable and scalable connections between platforms.

\n

API testing helps identify early issues and is different from UI testing. An API receives requests and sends back responses through internet protocols including, HTTP and SMTP. API tests investigate applications that have varying API functionalities and vary the API call's parameters in different ways that verify functionality and expose failures.

\n

API testing can be done on the below aspects:

\n\n

Functional Testing checks API's functionality, Takes payload in the form of JSON or XML and provides the response code and response body.\nLoad Testing checks the performance under the specific load and determines how much traffic the API can handle before being overloaded.\nSecurity Testing checks vulnerabilities like authentication and sensitive data is encrypted over HTTP and includes penetration testing validating authentication.

\n

Advantages of API testing during Software development

\n

1. Time efficiency

\n

API Testing doesn't require GUI to be ready and it can be performed way early in the development cycle. The Automated API tests provide much quicker test results and significantly accelerate development workflows; thus, it helps you speed up the feedback loop and catch issues faster.

\n

In addition to that, API tests are significantly less time-consuming when compared to UI Tests. UI Tests spend much time rendering and loading the web pages and interface elements, whereas can execute API tests in seconds. Let's take an example where a user needs to register and login from UI takes at least 3 to 5 minutes, whereas API testing takes less than 30 seconds.

\n

2. Reduced costs

\n

It is very closely connected with time efficiency.

\n

The cost efficiency benefit is closely connected with the previous one. Automated API tests' increased execution speed leads to more effective/efficient resource consumption and lower overall testing costs.

\n

API tests can be executed as early as the business logic is defined and before any GUI testing. So it will help you to identify the issue at the early stage. Early identification means the less expensive it is to fix it and Reduces the cost of Application changes. API testing enables the QA team to detect and resolve issues before they become a production problem, keeping project costs at bay.

\n

3. Technology Independent

\n

API tests are Language Independent, Since the data is interchanged using JSON or XML and compromised HTTP requests and HTTP responses. So the QA team is free to choose the language of their choice that supports these technologies((JavaScript, Java, Ruby, Python, PHP, etc.).

\n

4. Greater tests stability

\n

While GUI's are dynamic and may change to accommodate new requests from stakeholders and users, API interfaces are very much stable. APIs typically come with detailed documentation, and any changes are reflected there so that QA engineers can adjust their test suites timely. And due to this inherent stability, API tests are also much easier to maintain.

\n

5. Improved test coverage

\n

Unlike unit tests, automated API tests are generally broader in scope and detail. While unit tests are focused on the limited functionality of components within a single application, problems often arise at the intersection where one layer's scope ends and the other begins.

\n

You won't find these issues with unit tests, but API-level tests are specifically designed to verify that all system components function as intended. API testing helps uncover potential defects in the interfaces, servers, and databases, improving the overall software quality and contributing to better user experiences.

\n

Efficiency gains associated with an API testing tool can include:

\n\n

Conclusion:\nAPI testing is recognized as a better fit for Continuous Testing in Agile methodologies. Not adequately tested APIs may cause issues at the API application and the calling application. It is a necessary test in software engineering.

\n","frontmatter":{"title":"What is API Testing? - Discover the Benefits","author":{"id":"Surendranath Reddy Birudala","github":"reddysuren","avatar":null},"date":"February 12, 2021","updated_date":null,"tags":["Automation","API Testing","Agile","Benefits"],"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.680672268907563,"src":"/static/80a2124798188a2366a8093c6f4d4afc/71802/api-testing.webp","srcSet":"/static/80a2124798188a2366a8093c6f4d4afc/61e93/api-testing.webp 200w,\n/static/80a2124798188a2366a8093c6f4d4afc/1f5c5/api-testing.webp 400w,\n/static/80a2124798188a2366a8093c6f4d4afc/71802/api-testing.webp 770w","sizes":"(max-width: 770px) 100vw, 770px"}}}},"fields":{"authorId":"Surendranath Reddy Birudala","slug":"/engineering/api-testing-and-benefits/"}}},{"node":{"id":"f982d599-d35c-51b5-a882-680c83d70e52","html":"

What is Rest?

\n

Representational State Transfer in short-form as REST defines a set of constraints for creating Web Services.\nRest API is the most-used web service technology nowadays, and it's an almost meaningless description. A REST API is a way to communicate for two computer systems over HTTP, which is similar to web browsers and servers.

\n

What is BDD?

\n

BDD stands for Behavior Driven Development (BDD). Nowadays, many Organizations, to get a better advantage of testing, are taking a step forward.

\n\n

What is Cucumber?

\n

A cucumber is an approach that supports BDD. It allows you to write tests that anyone can understand, irrespective of their technical knowledge. In BDD, users (business analysts, product owners, developers, etc..). We need to first write scenarios or acceptance tests that describe the system's behavior from the customer's point of view for review and sign-off by the product owners before developers start actual development.

\n

What are the Prerequisites to Test Rest API using Cucumber?

\n\n

Steps to Install Java

\n
http://www.oracle.com/technetwork/java/javase/downloads/index.html
\n

Download JDK from the above link and install it\nSet the Environment Variable on System Properties

\n
Right Click on My PC -> Properties -> Advanced System Settings -> Environment Variables -> Create New -> provide path of JDK
\n

Steps to Install Eclipse

\n\n

Steps to Install Maven

\n\n

Configuring Cucumber with Maven

\n\n

Now we need three Important files.

\n\n

Feature File: It's a entry point to the cucumber. We use Gherkins to write the feature file. This is the file where you will describe your descriptive language(Gherkin uses simple English). A feature file can contains a Scenario or List of Scenario. A sample Feature file is below

\n
Feature: Login Functionality\n@validLogin\nScenario: User Should Login With Valid Credentials \n   Given Post Login API\n   When Provide Valid Credential\n   Then Status_code equals 200    \n   And  response contains IsLogin equals "true"\n@invalidLogin    \nScenario Outline: Email and Password Validation in Login API \n   Given Post Login API\n   When Provide different combinations to "<email>""<password>"\n   Then Status_code equals <statuscode>    \n   And  response contains message equals "<message>"\n   Examples:\n   |email     \t\t|password    | statuscode |  message\n   |          \t\t|            |   401      | Required email and password\n   | abc\t  \t|            |   401      | Email format is incorrect\n   | abc@mail7.io  \t|\t     |   401      | Required password\n   | abc@mail7.io   \t| password   |   401      | Email and Password combination Incorrect
\n

Save the above code as login.feature

\n\n

StepDefinition:\nNow you have your feature file ready with test scenarios defined. However, our job is not done yet. Cucumber doesn't know when should execute which part of code. So StepDefinition acts as an intermediate to your runner and feature file. It stores the mapping between each step of the scenario in the Feature file. So when you run the scenario, it will scan the stepDefination file to check matched glue.

\n

How to write step definition:\nWe have a chrome extension(Tidy Gherkin) to convert your feature into a step definition.
\nCopy your scenario from the feature file and paste it in Tidy Gherkin and click on Java Steps; copy the Java Steps.\nCreate a new file name a StepDefinition.java and paste the Java Steps

\n
package com.loginradius.login\nimport cucumber.api.java.en.Given;\nimport cucumber.api.java.en.When;\nimport cucumber.api.java.en.Then;\nimport cucumber.api.java.en.And;\nimport cucumber.api.junit.Cucumber;\nimport org.junit.runner.RunWith;\nimport static io.restassured.RestAssured.given;\nimport static org.testng.Assert.assertTrue;\nimport io.restassured.http.ContentType;\nimport io.restassured.response.Response;\nimport io.restassured.specification.RequestSpecification;\nimport io.restassured.RestAssured;\n\npublic class StepDefinition {\n\tprivate  static  final  String  BASE_URL  =  "https://www.loginradius.com";\n\tString email = "abcxyz@mail7.io;\n\tString password = "password";\n\tRequestSpecification request;\n\tprivate  static  Response response;\n\tprivate  static  String  jsonString;\n\n    @Given("Post Login API")\n    public void post_login_api() {\n\t    RestAssured.baseURI  =  BASE_URL;\n\t\trequest  =  RestAssured.given();\n\t\trequest.header("Content-Type",  "application/json");    \n    }\n    \n   @When("Provide Valid Credential")\n    public void provide_valid_credential() {\n      response  =  request.body("{ \\"userName\\":\\""  +  email  +  "\\", \\"password\\":\\""  +  password  +  "\\"}")\n\t\t\t\t\t\t  .post("/user/login");\t\n    }\n\n   @Then("Status_code equals {int}")\n    public void statuscode_equals_(int agr) {\n\t    Assert.assertEquals(arg, response.getStatusCode());\n    }\n\t\n\t@And("response contains IsPosted equals {string}")\n    public void response_contains_IsPosted_equals_(String message) {\n\t    Assert.assertEquals(message, getJsonPath(response, "IsPosted"));\n    }\t\n\n   @And("response contains message equals {string}")\n    public void response_contains_equals_(String message) {\n\t    Assert.assertEquals(message, getJsonPath(response, "message"));\n    }\n    \n\t@When("Provide different combinations to {string}, {string}")\n    public void provide_different_combinations_to_somethingsomething(String email, String password){\n\t    response = request.body("{ \\"userName\\":\\"" + email + "\\", \\"password\\":\\"" + password + "\\"}") .post("/user/login");\n    }\n\n\tpublic String getJsonPath(Response response, String key) {\n\t\tString resp = response.asString();\n\t\tJsonPath js = new JsonPath(resp);\n\t\treturn js.get(key).toString();\n\t}\n\t\n}
\n

Now we have Our Feature file and StepDefinition Ready, we need a runner file to run our Test Scenario's

\n

Runner File:\nA runner will help us to run the feature file and acts as an interlink between the feature file and StepDefinition Class\nBelow is the code which will help you to run the tests

\n
package runner;\nimport io.cucumber.testng.CucumberOptions;\n\n@CucumberOptions(\n\t\tfeatures= {"feature_files/login.feature"},\n        glue= {"step_definations/StepDefinitation.java"},\n        tags= "@validLogin",    // based on tags scenarios will run\n        monochrome=true, dryRun=false,\n\t\t)\t\npublic  class  TestRunner  {\n\n}
\n

Now We have Feature, StepDefinition, and runner files ready, We can run the runner file to see the results.

\n

Conclusion

\n

Cucumber is very useful in understanding the overall testing process without having coding knowledge. Since it uses simple English to write the feature file and makes developer, QA and other stakeholders on same page before starting the actual development.

\n","frontmatter":{"title":"Automating Rest API's using Cucumber and Java","author":{"id":"Surendranath Reddy Birudala","github":"reddysuren","avatar":null},"date":"November 05, 2020","updated_date":null,"tags":["Automation","Cucumber","Rest API","Java"],"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/1775ed5790237a2d1ac5fbda108bc357/58556/cucumber_rest_assured.webp","srcSet":"/static/1775ed5790237a2d1ac5fbda108bc357/61e93/cucumber_rest_assured.webp 200w,\n/static/1775ed5790237a2d1ac5fbda108bc357/1f5c5/cucumber_rest_assured.webp 400w,\n/static/1775ed5790237a2d1ac5fbda108bc357/58556/cucumber_rest_assured.webp 800w,\n/static/1775ed5790237a2d1ac5fbda108bc357/99238/cucumber_rest_assured.webp 1200w","sizes":"(max-width: 800px) 100vw, 800px"}}}},"fields":{"authorId":"Surendranath Reddy Birudala","slug":"/engineering/rest-api-cucumber-blog/"}}}]},"authorYaml":{"id":"Surendranath Reddy Birudala","bio":null,"github":"reddysuren","stackoverflow":null,"linkedin":null,"medium":null,"twitter":null,"avatar":null}},"pageContext":{"id":"Surendranath Reddy Birudala","__params":{"id":"surendranath-reddy-birudala"}}},"staticQueryHashes":["1171199041","1384082988","2100481360","23180105","528864852"]}