![](\"https://lh6.googleusercontent.com/ELzKfQlR5jHkRzeVW_9S0VxLD8vSfo2hJCvQxf37DZjwaod1Me05BzIs2Vk9unKneDda1PpI6TdmhvH7KnqFgCP0cRhIxORM9sfTn9RSTlTC40pwScwLLprVX2uu6sltu3kClQsc\")
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.
\nLet's discuss how, through how your team approaches your research plan, your team can get the benefits of API testing.
\nWhat 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.
\nAPI 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.
\nAPI testing can be done on the below aspects:
\nFunctional 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.
\nAdvantages of API testing during Software development
\n1. Time efficiency
\nAPI 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.
\nIn 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.
\n2. Reduced costs
\nIt is very closely connected with time efficiency.
\nThe 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.
\nAPI 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.
\n3. Technology Independent
\nAPI 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.).
\n4. Greater tests stability
\nWhile 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.
\n5. Improved test coverage
\nUnlike 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.
\nYou 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.
\nEfficiency gains associated with an API testing tool can include:
\nConclusion:\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":{"date":"February 12, 2021","updated_date":null,"title":"What is API Testing? - Discover the Benefits","tags":["Automation","API Testing","Agile","Benefits"],"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.680672268907563,"src":"/static/44fa40d81595c222eae816dc48759915/f571c/api-testing.png","srcSet":"/static/44fa40d81595c222eae816dc48759915/69585/api-testing.png 200w,\n/static/44fa40d81595c222eae816dc48759915/497c6/api-testing.png 400w,\n/static/44fa40d81595c222eae816dc48759915/f571c/api-testing.png 770w","sizes":"(max-width: 770px) 100vw, 770px"}}},"author":{"id":"Surendranath Reddy Birudala","github":"reddysuren","avatar":null}}}},{"node":{"fields":{"slug":"/engineering/rest-api-cucumber-blog/"},"html":"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.
\nBDD stands for Behavior Driven Development (BDD). Nowadays, many Organizations, to get a better advantage of testing, are taking a step forward.
\nA 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.
\nhttp://www.oracle.com/technetwork/java/javase/downloads/index.html Download JDK from the above link and install it\nSet the Environment Variable on System Properties
\nRight Click on My PC -> Properties -> Advanced System Settings -> Environment Variables -> Create New -> provide path of JDKSteps to Install Maven
\nCreate a Maven Project. Use below navigation.
\nOpen Eclipse -> File -> New -> Maven Project\n
Provide Group Id and Artifact Id and click on finish.
\nGroup Id: This element indicates the organization's unique identifier or group that created the project. The groupId is one of the key identifiers of a project and is typically based on your organization's fully qualified domain name. For example, com.loginradius is the designated groupId for all Maven plugins.
Artifact Id: it points to the unique base name of the primary artifact generated by this project. The main or primary artifact for a project is typically a JAR file. Secondary artifacts like source bundles also use the artifactId as part of their final name.
\nOpen pom.xml file to add necessary dependencies
\n<dependency>\n\t<groupId>io.cucumber</groupId>\n\t<artifactId>cucumber-java</artifactId>\n\t<version>6.6.0</version>\n</dependency>\n<dependency>\n\t<groupId>io.cucumber</groupId>\n\t<artifactId>cucumber-testng</artifactId>\n\t<version>6.6.0</version>\n</dependency>\n<dependency>\n\t<groupId>io.rest-assured</groupId>\n\t<artifactId>rest-assured</artifactId>\n\t<version>4.3.0</version>\n\t<scope>test</scope>\n</dependency>\n<dependency>\n\t<groupId>org.testng</groupId>\n\t<artifactId>testng</artifactId>\n\t<version>7.1.0</version>\n\t<scope>test</scope>\n</dependency>Now we need three Important files.
\nFeature 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
\nFeature: 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 IncorrectSave the above code as login.feature
\nStepDefinition:\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.
\nHow 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
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}Now we have Our Feature file and StepDefinition Ready, we need a runner file to run our Test Scenario's
\nRunner 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
\npackage 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}Now We have Feature, StepDefinition, and runner files ready, We can run the runner file to see the results.
\nCucumber 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":{"date":"November 05, 2020","updated_date":null,"title":"Automating Rest API's using Cucumber and Java","tags":["Automation","Cucumber","Rest API","Java"],"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/6185494b9a177d30a2dc78ccaca79e14/ee604/cucumber_rest_assured.png","srcSet":"/static/6185494b9a177d30a2dc78ccaca79e14/69585/cucumber_rest_assured.png 200w,\n/static/6185494b9a177d30a2dc78ccaca79e14/497c6/cucumber_rest_assured.png 400w,\n/static/6185494b9a177d30a2dc78ccaca79e14/ee604/cucumber_rest_assured.png 800w,\n/static/6185494b9a177d30a2dc78ccaca79e14/f3583/cucumber_rest_assured.png 1200w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Surendranath Reddy Birudala","github":"reddysuren","avatar":null}}}},{"node":{"fields":{"slug":"/engineering/importance-of-rpa/"},"html":"In definitive words, we can say ** \"Impersonating human activities in a sequential fashion to achieve a designated result without any manual intervention is known as Robotic Process Automation.\"**
\nThere are many benefits of robotic process automation, depending on the industries. I have listed a few common benefits across all the business domains and industries.
\nAny business's success depends on how deep they understand the customers, or rather, I should say targeted customers. And this is one of the fundamental challenges for companies.
\nIntelligent automation through RPA can be implemented to understand user behavior, helping companies in decision making for their targeted customers and growth.
\nRPA is the most sought after solution in this technology-driven era to reduce the investment being done on manual tasks and get the best of the employees by allowing them to innovate rather than doing monotonous work. Multiple studies say that rolling out RPA, and thoughtful implementation can save approx 30-35% of companies' costs being spent on non-productive and repetitive tasks.
\nA report by ICO (Information Commissioner's office) says that 90% of a data breach between 2017 and 2018 happened due to human error. Human minds have certain limitations. We can't always be attentive 100%. And the moment we lose attention, we become vulnerable to make mistakes.\nBut Robots, once defined/built, can have unlimited attention and can work endlessly without any distractions. And that gives the ability to make no mistakes.
\nHumans have their limitations, capacity to work. But robots, on the other hand, have no measure of capacity. If developed smartly, they can work for every millisecond. And this gives unlimited possibilities for any company to run their businesses without worrying about productivity.
\nBusiness process outsourcing(BPO) always strives for heftiness in productivity with minimal cost. With the efficient use of RPA, the BPO's can eventually reduce a lot of operating expenses and make more effective utilization of their workforce. As robots can work 24/7, productivity can be increased tremendously. Apart from repetitive work automation, the industry also has a lot of back-office work, which is purely rule-based, and the same can be achieved with better security and audits. Report generation, data analysis are the other tasks that can also be done through RPA. Some more examples can be
\nMost innovations, along with technological advancement, have been seen in the banking sector. As per the reports, the BFSI domain holds the largest share in the year 2019 to apply RPA.
\nRPA has a surfeit of applications in banking covering from customer service to compliance nearly everything. The following are a few examples.
\nThe medical industry across the globe has always been a sector that is continuously striving for improvement. Providing the best health care services for a broad range of population is a real challenge in both operational and organizational. There are numerous use-cases in the medical industry where patients and hospitals can leverage the benefits.\nSuch as :
\nInsurance is an industry which deals with vast amounts of data and processes. With the help, RPA insurance providers are now capable of merging front-end and back-end operations resulting in reducing cost and manual intervention.\nLeslie Willcocks professor at LSE, said that * \"In an insurer we studied, there was a particular process where it used to take two days to handle 500 premium advice notes. It now takes 30 minutes\"*\nThis much processing was made by implementing RPA. Apart from the front-end or back-end automation, there can be many other use-cases, for example
\nThere are many more benefits of robotic process automation, depending on the industries.\nA survey by Deloitte says that RPA continues to meet and exceed expectations across multiple dimensions, including :\n92% on Improved Compliance\n90% Improved quality and accuracy\n86% improvement in productivity and\n59% cost reduction.
\nThey say that with the current pace, RPA will have achieved near-universal adoption within the next five years.
\n","frontmatter":{"date":"October 23, 2020","updated_date":null,"title":"Why RPA is important for businesses","tags":["Engineering","RPA","Automation"],"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.5037593984962405,"src":"/static/f2993d36b93dfde7b755c69581762a74/14b42/RPA.jpg","srcSet":"/static/f2993d36b93dfde7b755c69581762a74/f836f/RPA.jpg 200w,\n/static/f2993d36b93dfde7b755c69581762a74/2244e/RPA.jpg 400w,\n/static/f2993d36b93dfde7b755c69581762a74/14b42/RPA.jpg 800w,\n/static/f2993d36b93dfde7b755c69581762a74/9a763/RPA.jpg 1050w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Vikram Jain","github":null,"avatar":null}}}},{"node":{"fields":{"slug":"/engineering/roadmap-idx-autotester/"},"html":"We're delightfully Announcing the upcoming releases of LoginRadius Identity-Experience-Framework Open-Source Automation
\nThese full-version releases will include more test coverage and major changes with several improvements & code optimizations, the details have been given below.
\nThe below changes are planned to go live in multiple scheduled major releases starting with mid of June 2020.
\n\nCI/CD pipelines for automation is to make everyday development tasks simple that can save time and reduce human intervention to check them every single code commit.
\n
headless mode\n\nWe are not just delivering automation we deliver values to our customers, some useful tips \"to working with selenium and nightwatch\" can be expected with this release
\n
\n\nAlthough current configuration does not support different browsers, still you can run on any browser by making few changes in nightwatch.json detailed guide is here
\n
optional and disabled email verification flows.multifactor-authenticationIt is agreed that we are committed to delivering you a seamless experience in automation, but still, if you face any issue or need any enhancements, please report us here
\n\n","frontmatter":{"date":"June 30, 2020","updated_date":null,"title":"Roadmap of idx-auto-tester","tags":["Automation","idx","roadmap"],"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7699115044247788,"src":"/static/b5c43b2bffb92542e899a8b9837bd4c5/ee604/roadmap_idx_auto_tester.png","srcSet":"/static/b5c43b2bffb92542e899a8b9837bd4c5/69585/roadmap_idx_auto_tester.png 200w,\n/static/b5c43b2bffb92542e899a8b9837bd4c5/497c6/roadmap_idx_auto_tester.png 400w,\n/static/b5c43b2bffb92542e899a8b9837bd4c5/ee604/roadmap_idx_auto_tester.png 800w,\n/static/b5c43b2bffb92542e899a8b9837bd4c5/f3583/roadmap_idx_auto_tester.png 1200w,\n/static/b5c43b2bffb92542e899a8b9837bd4c5/e4d72/roadmap_idx_auto_tester.png 1280w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Rakesh Pareek","github":"rkpareek","avatar":null}}}},{"node":{"fields":{"slug":"/engineering/introduction-of-idx-auto-tester/"},"html":"Idx-Auto-Tester is LoginRadius Identify Experience Automation Framework which refers to IEF Automation, is an open-source automation framework built-in Nightwatch| Node.js tool with delivering all the standard authentication cases of LoginRadius Identity Experience.\nThis automation framework has been created for The LoginRadius Identity Experience Framework which is a ready-to-use solution that provides predefined layouts for all necessary authentication actions. It has all of the user accounts flows available, such as login, registration, forgotten password, and profile management.
\nWe used Nightwatch.js end-to-end testing framework to create our Idx-Auto-Tester. This framework relies on Selenium and provides several commands and assertions within the framework to perform operations on DOM elements. It internally uses the powerful W3C Webdriver API or the Selenium Webdriver and simplifies writing end-to-end automated tests in Node.js and effortlessly sets up for Continuous Integration.
\nNightwatch uses JavaScript language (Node.js) and CSS/XPath to identify an element. It has Built-in command-line test runner which can run the tests either sequentially or in parallel, together, by group, tags, or by single.
\nStep 1: Download and Install Java.
\nStep 2: Install Node.js.
\nStep 3: Install Nightwatch. In the command line, navigate to any directory and type
\n npm install -g nightwatch (here ‘g’ is for installing globally).Step 4: Create a folder structure as shown below where Project is the root.
\nStep 5. Now it is required to install selenium-server-standalone.jar and chromedriver.exe along with other dependencies to execute test cases.
\nAs all the dependencies are added in nightwatch.json, so by executing below command, these will be added in node_modules folder
\n npm installNow we have installed all the dependencies and configuration setup for the automation framework. Nightwatch.js offers an in-built test runner which expects a JSON configuration file to be passed. The default configuration file is nightwatch.json which should be present in the project’s root directory.
\nStep 6. In the root folder, create “nightwatch.js” file and place the following line:
\nrequire("nightwatch/bin/runner.js")Step 7. Now create nightwatch.json configuration file with the configurations mentioned as below code snippet for testing with Selenium and JavaScript.
{\n "src_folders": ["test"],\n "output_folder": "tests_output",\n "custom_commands_path": "helpers/custom-commands",\n "custom_assertions_path": "",\n "page_objects_path": "",\n "globals_path": "",\n "test_workers": {\n "enabled": false,\n "workers": 3\n },\n\n "selenium": {\n "start_process": true,\n "server_path": "node_modules/selenium-server-standalone-jar/jar/selenium-server-standalone-3.13.0.jar",\n "log_path": "",\n "host": "127.0.0.1",\n "port": 4444,\n "cli_args": {\n "webdriver.chrome.driver": "node_modules/chromedriver/lib/chromedriver/chromedriver.exe",\n "webdriver.ie.driver": ""\n }\n },\n\n "test_settings": {\n "default": {\n "skip_testcases_on_fail": false,\n "launch_url": "http://localhost",\n "selenium_port": 4444,\n "selenium_host": "127.0.0.1",\n "silent": true,\n "screenshots": {\n "enabled": true,\n "path": "screenshots"\n },\n "desiredCapabilities": {\n "browserName": "chrome",\n "javascriptEnabled": false,\n "acceptSslCerts": false,\n "chromeOptions": {\n "args": ["--headless-none"]\n }\n }\n },\n "firefox": {\n "desiredCapabilities": {\n "browserName": "firefox",\n "javascriptEnabled": true,\n "acceptSslCerts": true,\n "cli_args": {\n "globals": {\n "env": "fire fox"\n }\n }\n }\n },\n\n "ie": {\n "desiredCapabilities": {\n "browserName": "internet explorer",\n "javascriptEnabled": true,\n "acceptSslCerts": true,\n "cli_args": {\n "globals": {\n "env": "ie"\n }\n }\n }\n }\n }\n}Step 8. Now its time to design test case of any scenario, same as created in our Idx-Auto-Tester Framework under test folder named as TC01UserLogin
\nTo create functions/methods, we used nightwatch custom commands approach to create commands for all the required functions under custom-commands folder, like as there is command created for createUser.js which used to create the user and call it under test case.
\n\n\nNote: We are using 'Function-style commands' of Nightwatch to create command to resolve the asynchronous queueing system problem while running the test case.
\n
Step 9. The final thing we are required to do is to execute the tests from the base directory of the project using the command:
\nnpm test\n\nImportant Tip : A script has been added in package.json to define test execution command:
\n
"scripts":\n {\n "test": "node nightwatch.js --reporter html-reporter.js test"\n }This command will validate the tests and dependencies and then execute the test suite, which will open up the mentioned browser and execute the desired test steps.
\nIt is required to update the configuration to execute the tests in parallel by enabling the test_workers as true. This will enable parallel execution and execute all tests on a defined number of workers.
\n "test_workers": {\n "enabled": true,\n "workers": 3\n },In this framework design, we have covered various flows of LoginRadius Identity Experience Automation testing with Selenium Javascript. I hope we are now clear about the approach for an end-to-end automation testing with Selenium JavaScript using Nightwatch.js with the reference of Idx-Auto-Tester. We are aware of all the prerequisites required for setting up Nightwatch.js. It automates the entire test suite quickly with minimal configuration and is readable as well as easy to update. Our framework is also capable to use the best feature provided by Nightwatch.js framework which is the parallel testing of cases that proves to be time-efficient. The test results can directly be read from the terminal and also stored at a specified output folder.
\n","frontmatter":{"date":"June 22, 2020","updated_date":null,"title":"Introduction of Idx-Auto-Tester","tags":["Automation","Idx-Auto-Tester"],"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7699115044247788,"src":"/static/0081dfe350298b300d58aa44264cb5e8/ee604/idx-auto-tester.png","srcSet":"/static/0081dfe350298b300d58aa44264cb5e8/69585/idx-auto-tester.png 200w,\n/static/0081dfe350298b300d58aa44264cb5e8/497c6/idx-auto-tester.png 400w,\n/static/0081dfe350298b300d58aa44264cb5e8/ee604/idx-auto-tester.png 800w,\n/static/0081dfe350298b300d58aa44264cb5e8/f3583/idx-auto-tester.png 1200w,\n/static/0081dfe350298b300d58aa44264cb5e8/e4d72/idx-auto-tester.png 1280w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Himanshi Sharma","github":"Himanshi0512","avatar":null}}}},{"node":{"fields":{"slug":"/engineering/opensource-automation-for-identity-experience-framework/"},"html":"We're delightfully announcing the open source automation suite to test all the standard authentication cases of LoginRadius Identity Experience Framework.\nThe details have been given below.
\nIdentity Experience Framework is a ready-to-use solution for all the necessary actions. It is a set of registration, authentication, and related web pages such as forgot password, profile. It allows you to customize the UI and UX elements as per your requirements.
\nThe Standard Authentication Functionality which is available with LoginRadius Identity Experience Framework can be tested via using these automation scripts. By running all the scripts, you can ensure your implementation.
\nNote: Currently, the test cases are scripted to run with only 'Required Email Verification' flow.
\nWe are continuously working on improving this automation suite and soon we will be announcing the roadmap for automation suite.
\n","frontmatter":{"date":"June 04, 2020","updated_date":null,"title":"Automation for Identity Experience Framework is now open-source !!!","tags":["OpenSource","Automation"],"coverImage":{"childImageSharp":{"fluid":{"aspectRatio":1.7699115044247788,"src":"/static/cf1bf1337d69f66b3411484def3a3c58/ee604/automation_ief.png","srcSet":"/static/cf1bf1337d69f66b3411484def3a3c58/69585/automation_ief.png 200w,\n/static/cf1bf1337d69f66b3411484def3a3c58/497c6/automation_ief.png 400w,\n/static/cf1bf1337d69f66b3411484def3a3c58/ee604/automation_ief.png 800w,\n/static/cf1bf1337d69f66b3411484def3a3c58/f3583/automation_ief.png 1200w,\n/static/cf1bf1337d69f66b3411484def3a3c58/e4d72/automation_ief.png 1280w","sizes":"(max-width: 800px) 100vw, 800px"}}},"author":{"id":"Sudhey Sharma","github":"sudheysharma","avatar":null}}}}]}},"pageContext":{"tag":"Automation"}},"staticQueryHashes":["1171199041","1384082988","2100481360","23180105","528864852"]}