by admin | Nov 6, 2018 | Automation Testing, Blog |
Knowing the difference between RPA and automation testing is important for RPA consultants & Test Automation Engineers. Nowadays we come across questions – Is RPA achievable using Automation Tool? Can we write automation script using RPA Tools?
Let’s understand the difference between these two.
Robotic Process Automation (RPA) is the use of software robots, artificial intelligence (AI), and possibly machine learning to handle high-volume, repeatable rules-based enterprise tasks that previously required a human to perform.
If you have an automation testing team in place & wish to try RPA using Selenium and Java then you are going in the wrong direction. You can write scripts for data scraping, OCR, Excel handling, and PDF handling using Test Automation tool & Java. However, why is automation tool not right choice for RPA?
The reasons are – RPA needs Production environment. So when there is a change in business process, you need to update the RPA process flow quickly. If your RPA flows are scripted using Automation Tool, then updating the scripts needs time since you have coded the business process.
If you fail to update the flow as and when needed, your RPA implementation has serious flaws or your team has limited knowledge in RPA tool.
Automated regression test suite executes test cases one by one. Each test case should be independent. For example: If 5 test cases have failed out of 150, then it does not mean that your automation implementation is not good.
However, for RPA, the execution order matters and each execution should happen based on rules and flow decisions without failures.
Both automation testing and RPA automate Repetitive and boring tasks. We hope that this article answers What’s the Difference between Automation Testing and RPA?
In the subsequent blog articles, we will publish more on RPA and tools.
by admin | Aug 15, 2018 | Automation Testing, Blog |
The prospect of reviewing a new test automation tool is always an exciting one for any software testing company. Choosing the right tool for product testing for anyone in the software testing community becomes easier with the help of unbiased Test Automation Tool reviews by experienced test automation experts. In this blog, we look at each feature of Katalon Studio in detail.
The Installation Process
Click the link below and complete the Signup procedure to download Katalon Studio.
https://www.katalon.com
Installation is not needed. All you have to do is unzip the downloaded file in your desired location.
The Types of Applications that can be tested using Katalon
Web, Mobile apps & Web Service can be automated.
A Recommendation to the Katalon Team: Desktop App Automation Testing will increase the functionality of the tool.
Pricing for the Tool itself and Technical Support
While the tool itself costs nothing, the price for technical assistance is 249 USD per month
| Type |
No. of accounts |
Pricing |
| Business Support |
1 |
2500 USD per year |
| Enterprise Support |
3 |
5000 USD per year |
Custom Keyword Development
This is one of the most noteworthy features of the Katalon testing tool. The keyword can be created using Groovy scripting and can also be called at any point in the test flow.
There also exist a sufficient amount of additional built-in keywords.
Object Identification
? Nested Identification
All available locators can be used in Selenium. As shown below, any WebElement in Selenium can be identified using multiple levels of nested identification.
driver.findElement(By.name("btn2"));
elemnt.findElement(By.name("codoid")).findElement(By.name("Test Company"));
Katalon, however, only permits the use of 1 level of nested identification.
? Switching Frames and Browser Windows
? In order to switch frames, one has to first define a frame in Test Object with the Object Identification Details and then call the Switch to Frame keyword.
? Windows can be switched using Index, URL & Title.
Manual View & Script View
Manual View facilitates easy script development. The required keyword and test object for a test step can be selected in Manual View.
You can view all the steps which are added in Manual View in Script View as well. This feature gives more flexibility to troubleshoot your scripts. And you can modify the scripts from Script View and the changes can be seen in Manual View.
One also has the capability of viewing all the steps that were added in Manual View, in Script View. This feature allows for more flexibility when it comes to troubleshooting scripts. There is also the provision for modifying scripts from Script View and observing the changes in Manual View.
A Recommendation to the Katalon Team: It would be better if the script view editor could highlight scripting errors instead of just underlining them.
Jira Integration
A Jira bug ticket can be created while troubleshooting failures from Katalon Test Reports.
Looping
Looping is an indispensable feature of any test automation framework. Katalon allows for the usage of For & While loops
The restriction of nested looping is a daunting task for any automation test. Katalon Studio is awarded a 5-star rating for enabling nested looping.
Conditional Statement
Similar to looping, Katalon also allows nested conditional statements. There is, however a disadvantage to using conditional statements in Katalon. In order to decide True & False statements, the outcome of a keyword call in a variable and input in the Conditional Statement need to be saved. This can prove to be a burdensome procedure.
A Recommendation to the Katalon Team: The enabling of keyword calls in Conditional Statements, in order to decide between the execution of True and False Statements would be a useful feature to have.
Hard and Soft Step
Assuming a mandatory test step has failed and you would like to halt the test execution, the failure handling in Katalon can be configured as shown below.
Object Spying
Katalon allows for the spying on of Web and Mobile Objects. The provision for Object Spying in a freeware test automation tool is a definite bonus for automation testers.
Katalon Studio supports spying AUT on IE, Chrome & Firefox browsers.
Hooking
The following hooks which are executed before or after test case & test suite are supported by Katalon. Test case status, ID & variables can also be obtained inside these hooks.
Before & After Test Case
Before & After Test Suite
A Recommendation to the Katalon Team: The provision for Tag based hook calling would be beneficial.
Git Integration
The SCM feature is essential for automated script development as it permits the tracking of code changes while facilitating effective work coordination.
The feature for Git Integration in Katalon Studio can be enabled from Preferences.
Execution Video Recording
Recorded test execution is a great reference material. Katalon has a video recorder which can be enabled for Passed or Failed test cases or both.
The feature of recording test execution works great as reference material. The video recorder feature on Katalon can be enabled for either Passed or Failed test cases or even both.
Email Notification
There exists on Katalon, a Template for receiving Email notifications. The content can be customized in accordance with changing requirements.
(more…)
by admin | May 1, 2018 | Automation Testing, Fixed, Blog |
Rerunning Cucumber failed scenarios is a great value add for your automation test suites. Sometimes, your scripts may fail because of network latency and test bed slowness. Rerunning scripts will reduce the number of failures.
However, you need to monitor the scripts which are always failing in the first attempt. In this blog article, we will walk you through how to rerun jvm-Cucumber failed scenarios.
Step #1
Configure where you want to store failed scenario details in Runner class
package sample.cukes;
import cucumber.api.CucumberOptions;
import cucumber.api.testng.AbstractTestNGCucumberTests;
@CucumberOptions(
features = "src/test/resources/features/Sample.feature", monochrome = true,
plugin = {
"pretty", "html:target/cucumber-report/single",
"json:target/cucumber-report/single/cucumber.json",
"rerun:rerun/failed_scenarios.txt"},
glue = {"common","sample"}
)
public class SampleCukesTest extends AbstractTestNGCucumberTests {}
Note: Use rerun variable in CucumberOptions to store the failed scenarios.
Step #2
Create a new Runner class to run the failed scenarios.
package sample.cukes;
import cucumber.api.CucumberOptions;
import cucumber.api.testng.AbstractTestNGCucumberTests;
@CucumberOptions(
features = {"@rerun/failed_scenarios.txt"},
monochrome = true,
plugin = {
"pretty", "html:target/cucumber-report/single",
"json:target/cucumber-report/single/rerun_cucumber.json"},
glue = {"common","sample"}
)
public class FailureRerun extends AbstractTestNGCucumberTests {}
Note: In the ‘features’ variable, you need mention the failed_scenarios.txt file and don’t forget that you must mention ‘@’ symbol before the file path.
If you are running your automated test scripts from Jenkins, you can create and configure a downstream job to run the failed scenarios.
