Table of Contents

• 1. What is TestNG?
• 2. Why use TestNG with Selenium?
• 3. Installation of TestNG
• 4. Setting up a TestNG Project
• 5. Creating a TestNG TestFile
• 6. Run Test Case and Generate Report
• 7. Asserts in TestNG
• 8. Summary

1. What is TestNG?

TestNG is an open-source automated testing framework with flexible and powerful features. It is inspired by JUnit and NUnit but with some additional advantages and functionalities. TestNG gives the developers to build tests with easy annotations, sequencing, grouping, and parameterizing.

The ability to generate test reports to get an idea on what test cases passed, failed, and skipped makes it even stronger and a better choice for a test automation framework.

2. Why use TestNG with Selenium?

Selenium does not come with test report generating options. The best thing we can do is printing the results to the console. But with TestNG, we can produce test results in a proper report format through which we can get an overall idea for better analysis. Besides this, there are many other additional advantages TestNG provides.

• Produces test reports in different formats with clear ides of what test passed, failed, and skipped.
• The same test cases can be executed several times by just using a keyword.
• Test cases can be prioritized and grouped and converted to a .xml file.
• Test cases can be run in multiple browsers simultaneously.
• Ability to integrate with tools like Maven and Jenkins.
• Supports parallel testing and load testing.
• Easy and understandable annotations like ‘@’
• It provides the ability to parameterize data.

3. Installation of TestNG

Installing TestNG to Eclipse is pretty easy since it comes as a plugin obtained from Eclipse Marketplace.

• First, Eclipse IDE should be installed on your computer, and it can be downloaded from their website.

• Next, launch Eclipse and go to Help in the menubar and select Eclipse Marketplace.

• Once it is clicked, the Eclipse Marketplace Modal will be displayed. Then you will have to type in “TestNG” and search for it. Once the result comes up, click Install.

4. Setting up a TestNG Project

• Once it is installed, we can create a new Java project by clicking File > New> Project

• Give the name “myTestNGProject” and click Finish

• Next is to import the libraries into the project. Go to project properties > Java Build Path

• Under libraries tab select Add Libraries.

• Then select TestNG and click Next, then Finish.

• Next, add the Selenium jar files into the project the same way as above but select ‘Add External Jars’ under the library tab, and select the .lib files from the folder they are saved at. These library files can be downloaded here.

5. Creating a TestNG TestFile

• Right-click on the “src” file of the project created earlier and select New >Other

• Select the TestNG class under the TestNG folder and click Next.

• Type in the following values in text boxes given and click Finish.

• Once it is done, a default template can be seen in our class created by TestNG

• To create a test case, the following code will be used. The code below will fetch the site https://www.airbnb.com/, verify the title, print out the result, and close the browser.

package myTestNGPackage;

import org.testng.annotations.Test;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.firefox.FirefoxDriver;
import org.testng.Assert;

public class myTestNGFile {
  
  public String baseUrl = "https://www.airbnb.com/";
  String driverPath = "C:\\geckodriver\\geckodriver.exe";
  public WebDriver driver ; 
  @Test
  public void f() {
     
     System.out.println("launching firefox browser"); 
      System.setProperty("webdriver.gecko.driver", driverPath);
      driver = new FirefoxDriver();
      driver.get(baseUrl);
      String expectedTitle = "Vacation Rentals, Homes, Experiences & Places - Airbnb";
      String actualTitle = driver.getTitle();
      Assert.assertEquals(actualTitle, expectedTitle);
      driver.close();
  }
}

6. Run Test Case and Generate Report

Tests can be run the usual way we run a test in Eclipse, but there will be 2 reports. One in the console, which is text-based, and the other in the TestNG result window, which is graphical.

To create HTML reports, right-click on the project, and click Refresh. Then you can see a new folder called “test-output”. Expand it and view the files. There will be a file called index.html. Double click on it to view the report.

The report will open up in the default browser of Eclipse. It is a detailed view of the tests executed, their information, and test results.

7. Asserts in TestNG

Assertions are used to validate test scripts and show whether they have passed or failed. In the above example, we have used Assert.assertEqual(actual value, expected value). If the values do not match the assert with a throw, an exception and the test case will fail.

There are mainly two types of Assertions. One is Hard Assertions, which are default in TestNG and are used to stop a test immediately when an assertion fails. The second one is Soft Assertion, which is a custom assertion that is used when a test has to continue even when an assertion fails in the sequence.

8. Summary

• TestNG is powerful and a flexible testing framework.
• It is inspired by JUnit and NUnit but has better functionalities.
• Using TestNG with Selenium provides many great advantages, including the ability to produce test reports with better visibility of what test cases passed, failed, or skipped.
• To use TestNG in Selenium, we need to create a TestNG class and write the test script on it.
• We use Assertions to verify the status of the test in the middle of the test run.
• Once a test script runs in TestNG, it produces two outputs. One in the console and the other in the TestNG result window.
• After running the test suite, we can obtain the test report in the form of a .html file.

The post How To Use TestNG with Selenium appeared first on Automation Dojos.

Table of Contents

• 1. Selenium and Selenium Web Driver
• 2. Setting-Up the Environment
• 3. Test Script with Selenium Web Driver
  • 3.1) Creating a project
  • 3.2) Creating a Class
• 4. Code a Simple Selenium Script
• 5. Running the test

Testing is a critical step in the Software Development Life Cycle. Software testing helps to ensure the quality and effectiveness of the final product.

Automated Functional testing automates the process of testing and validating each functionality in the software through the execution of pre-defined Automation scripts. This is mainly done for test cases that need to be repeated and are tedious to perform manually.

1. Selenium and Selenium Web Driver?

Selenium is a collection of specialized tools for automating the testing process of web-based applications. This free and open-source tool can be used across different browsers and platforms.

Selenium Web driver is a browser automated framework and accepts written scripts and controls browsers directly. Furthermore, it supports test scripts written in several different languages such as Java, JavaScript, PHP, Python, and C#.

2. Setting-Up the Environment

The following prerequisites must be satisfied to create and run automated test scripts using Selenium.

3. Test Script with Selenium Web Driver

3.1) Creating a project

1. Launch Eclipse from the Start Menu or by double-clicking “eclipse.exe” in the folder “eclipse” where it was installed.
2. To create a new Project, go to File > New and select

3. Now name the project. I’ll be using “FirstWebDriverProject‘.

4. Then click “Finish”. The project will be created and displayed in the Package Explorer.

5. Right-click the project and select New >Package

6. Name the package “newPackage” and click Finish.

3.2) Creating a Class

1. Right-click on the package and select New > Class.

2. Give the name ‘myClass’ and click Finish.

4. Code a Simple Selenium Script

We will now use the new Class to write a script in Selenium Web Driver using Firefox. It will fetch the site https://www.airbnb.com/, verify the title, print out the result and close the browser.

package newPackage;

import org.openqa.selenium.WebDriver;
import org.openqa.selenium.firefox.FirefoxDriver;

public class myClass {

   public static void main(String[]args) throws InterruptedException{
      System.setProperty("webdriver.gecko.driver", "C:\\geckodriver\\geckodriver.exe");
      
      WebDriver driver = new FirefoxDriver();
      
      String baseUrl = "https://www.airbnb.com/";
        String expectedTitle = "Vacation Rentals, Homes, Experiences & Places - Airbnb";
        String actualTitle="";
      driver.get(baseUrl);
      actualTitle = driver.getTitle();
      if (actualTitle.contentEquals(expectedTitle)){
         System.out.println("Test Passed!");

         } else {

         System.out.println("Test Failed");}	 
      driver.close();
      System.exit(0);
   }
   
}

Let’s analyse and understand this code in bit detail:

if (actualTitle.contentEquals(expectedTitle)) {

System.out.println("Test Passed!");

} else {

System.out.println("Test Failed");}

5. Running the test

To run the test script, click Run > Run in the Eclipse menu. Alternatively, you can press Ctrl + F11.

Once everything is done Eclipse will print out the result in its console.

This is just a simple example. There is a lot more that can be done with Selenium. Use this example as the beginning of your Selenium journey!

The post Getting Started with Selenium WebDriver appeared first on Automation Dojos.

Table of Contents

• Testing Challenges in Traditional Setup
• Cloud Testing
• Benefits of Cloud Testing
• Cloud Testing Providers

The ‘Cloud Computing’ technology has revolutionized the IT industry and it has something good to offer to the testing industry too. After Iaas, PaaS, and SaaS concepts, there is a new testing area called Testing as a Service (TaaS) that is making waves in recent times. Increasing IT costs, shrinking budgets and growing business demands pose a great challenge for organizations. Testing as a Service or Cloud Testing answers these challenges by providing cost-effective test solutions built using cutting-edge technologies.

Testing Challenges in Traditional Setup

The first and foremost challenge in today’s organizational setup is the limited budget for the testing team. With changing economic conditions and growing competition, companies have to optimize available resources to the fullest. Allocating separate budgets for testing projects is cumbersome. Moreover, there are strict deadlines that need to be met. Secondly, the testing team creates a large number of test cases that are mostly unused. At times, they are used only once. Thirdly, traditional testing procedures are restricted by geographical locations. Most importantly, there is rapid development in the testing tools segment. World-class testing tools that are engineered with cutting-edge technologies are implemented by large enterprises and small and medium businesses cannot afford to lay a hand on these tools. Cloud Testing offers the luxury of using these cutting-edge technologies at an affordable price. Moreover, TaaS brings greater levels of agility into workflow procedures while improving the performance of the system.

Cloud Testing

Cloud Testing is the new trend in the testing tools segment that uses the cloud environment to simulate real-time traffic. It uses different testing modules to gauge the performance of an application. With cloud-based services dominating the technology, there is a greater need for cloud-based testing.

Benefits of Cloud Testing

Testing as a Service is rapidly gaining momentum in recent times. The primal benefit of a cloud testing environment is the quick deployment of testing tools required for the project. Cloud Testing offers a wide range of testing tools that are built using cutting-edge technologies. Moreover, the testing environment is deployed within a quick time. The performance of the cloud-based testing tool is very good. By bringing agility into testing procedures, cloud testing tools reduce the time taken to identify non-critical defects as well as critical defects.

Most importantly, cloud testing allows businesses to leverage available resources to a maximum extent. You don’t have to invest in various testing modules that are not used most of the time. By paying only for the services used, businesses get the flexibility to optimize budgets and leverage resources. The downside of cloud testing is that it is not suited for some applications. However, the cloud testing environment is rapidly developing to provide a versatile range of services.

Cloud testing is again different from testing a cloud. While cloud testing is about testing an application in the cloud, testing the cloud deals with the evaluation of the cloud infrastructure, applications, and environments that are provided on demand. It is to make sure that the cloud infrastructure is performing according to its cloud computing business objectives.

Cloud Testing Providers

While the cloud testing environment is still new, there are few providers that offer quality testing software. HP Load Runner is one of the leading providers of cloud testing tools. SOASTA, Advaltis, and Cloud Assault are among other contenders for this place.

The ‘Cloud’ innovation is still on the move. Mobile TaaS is another cloud-based testing environment that is used to test mobile applications. With mobile applications created in great volumes, Mobile TaaS has much more to do in the coming days.

The post Introducing Testing-as-a-Service (TaaS) appeared first on Automation Dojos.

With rapidly changing financial conditions, businesses face the tough challenge of optimizing resources to produce maximum results. Choosing the right automation tool for functional testing is one of the important tasks in doing so.

The rising popularity and emerging technologies have brought in several testing tools into the market which makes it difficult for organizations to identify the right one for their testing needs.

You have to compare different testing tools and apply the functionality to your business processes to gauge the performance of the tool. Here are certain best practices that need to be followed while evaluating automated testing tools.

1. Feature set

When looking at the tool, one of the important aspects is the feature set. The first benefit of automation is the ease and efficiency it offers for testing purposes. This is what allows you to run automated scripts on multiple codes while you perform other tasks as well.

Object Recognition, Verification and Repository

Another important functionality required by an automated testing tool is the ability to recognize and validate objects while storing them in a repository. As you run multiple scripts, the tool identifies hundreds of objects, standard and custom ones. It should offer an effective mechanism to separately identify each object while associated object attributes as well.

Having a central repository is a desirable option. When you change the name of the object, would you be able to use the object without affecting any part of the application? So, the best thing is to check how the object name mapping system is designed for the tool.

Another desirable feature is image testing. The tool should recognize images and compare one with others. So, check if the tool supports Optical Character Recognition (OCR).

2. Minimum functionality

While having multiple features is always a great idea, it is of no use if the functionality of the tool is not up to the mark. There are certain basic functions that are performed on a regular basis and the automated tool should be able to produce high-quality results. Here are some of the minimum functionalities expected from an automated tool.

3. Usability

The third important aspect to look at is the Usability. Right from installing the product to using various functions, the tool should be easy to use. The installation should be simple and self-explanatory. And, check if coding knowledge is required to run scripts and how long does it take to run scripts. In addition, what does the tool offer for debugging tasks? Does the tool provide adequate documentation and support?

4. Performance

The performance of the automated tool while running multiple scripts is important as well. It is to be robust enough to support enterprise applications. Check how long it takes to create a script and what is the script running time. Moreover, does the tool offer test management tools to effectively track and monitor test progress? And another important consideration is the consistency of test results. The system requirements for the tool need to be considered as well.

 5. Technical Support

While the tool offers extensive features, there should be adequate help and support to resolve technical issues. Check out the support options offered by the tool. While some products offer dedicated support, open-source testing tools generally do not have one. They have large communities and forums wherein you can find resolutions to several issues. However, if you experience any new issue, you will have to create your own resolution or wait for someone to post one.

6. Price

Finally, the price is an important factor as well. Today, some of the leading automated testing tools available in the market are very expensive. At the same time, there are open-source testing tools that are free to download and use. However, it is not a good idea to directly look at the price.

If the tool is expensive, consider the sophistication offered by the tool.

Does it require knowledge and expertise of coding which in turn results in the recruitment of skilled testers? At the same time, if the testing is quick and effective, it improves the development cycle of the product and thereby increases your revenues

While considering the price, the total ROI needs to be calculated that includes the price, licensing, support and maintenance. There are times when staffing, testing time and complexity of testing impact the revenues of the company. So, consider all these factors.

The post Best Practices For Evaluating Automation Tool appeared first on Automation Dojos.

Table of Contents

• Essentials 1: Test Artefacts Repository
• Essentials 2: Error Handling and Recovery
• Essentials 3: Object Identification Method
• Essentials 4: Test Data Management
• Essentials 5: Result and Error Reporting
• Essentials 6: Function Libraries Repository

As we discussed the types of QTP/UFT frameworks earlier in our post ‘Traditional Framework Definitions‘. In continuation of that, this article talks about the ‘essential components of a typical framework.

Irrespective of the kind of framework you choose, whether it’s Data-Driven, Keyword Driven, or BPT Framework, etc., one must address the following components which are hereby cited hereby as ‘essentials’. These components shall serve as the fundamental building blocks of your framework.

Personally, my choice is always the so-called ‘Hybrid framework’. In such a framework at a lower level, you can create data in external files as in a data-driven approach, and creation of keywords as in keyword driven framework, while keeping Functional decomposition as an ‘Umbrella’ strategy. Now tailor it all together alongside your project requirements and you get a potential ‘Hybrid Framework’. It just gives you all the benefits in one!

Essentials 1: Test Artefacts Repository 

By test artefacts, we mean scripts, function library, object repository etc. and even including the test cycle results. Of course, using a shared central repository with reasonable versioning makes sense and hence the most obvious choice should be HP Quality Center and if it’s added with a bit of ALM related salt then nothing like it!

Following are some of the upfront benefits of choosing HPQC ALM as your test artefact repository :

Essentials 2: Error Handling and Recovery

There is no doubt that without proper error handling or lack of recovery scenario would land you frequently into debugging your test scripts, test environment or data. You may end up re-running your test cycle or tests multiple times due to interruption caused as a result of such script failures.

In many cases, a lack of error handling may also give false or invalid results as the script may just go over without capturing errors or failures and still marking the scripts as ‘passed’

Hence your script or code should be built with sufficient error handling and recovery scenarios. Error Handling can be implemented using QTP/UFT inbuilt ‘recovery scenario manager‘ or manually through custom scripting in your script of library code.:

Essentials 3: Object Identification Method

This is again one of the most important aspects of any automation framework. This basically means, ‘how your automation tool recognizes or identifies the AUT UI, UI elements/components’ etc.

With QTP/UFT you have the following choices for object identification. Which method you choose does steer your script development and usability aspect of the framework :

Essentials 4: Test Data Management

Test Data provisions and strategy is another important aspect that should be a part of a good framework. With data parameterization, your test data would be kept separate from the code. And this will ensure that the same code can be re-used for different sets of data.

There can be a variety of Test Data sources options such as excel files, database, text files and XML files. But generally, the best one is mostly Excel or CSV:

You should adhere to following considerations and best practices for test data :

Elapsed time in loading test data: ‘Should you load all data globally before triggering any test suite?’ or ‘Should you load test data per-test basis?’ Hence this generally calls for carefully choosing the data source and weighing against the loading strategy. As a case study, in one of the projects, I observed a lot of time spent in loading data for each test individual basis from a database source. Not a good idea due to time spent in connecting/disconnecting from the database over a network!

Essentials 5: Result and Error Reporting

Ideally, a separate Reporting component can be developed which is basically a collection of Library functions and procedures customized for reporting only. Depending upon the project requirements and effort available, this reporting component may generally make use of external databases (MSAccess), excel files or text log files to write the output of the tests. such a provision comes handy when you want to drill down to errors or failures by applying filters on databases or file output.

Avoid implementing reporting into individual scripts directly using reporter.reportevent, WScript.Echo, MsgBox or any such statement, instead you should at least develop a small separate module for such functionality into your function library

On a last note, an HTML based result report generally offers the best presentation and usability. A good framework would generally have such customized HTML based result reporting module.

Essentials 6: Function Libraries Repository

Supporting Libraries is again one of the most fundamental and required part of any good framework.

Below is one such best practices for libraries and scope of libraries that can be maintained:

The post Essentials of Typical QTP/UFT Framework appeared first on Automation Dojos.

Table of Contents

• Ease of use
• Features
  • TDS Code Editor
  • Real-time Syntax Checks
  • Full IntelliSense Support
  • Code Metrics
  • Real lines of code
  • Quality Center support
• The Performance
• The Price

While QTP offers greater flexibility to automate testing procedures, the IDE lacks certain professional features. A QTP license is expensive as well. Test Design Studio 2.0 from Patterson Consulting augments QTP software by providing an intuitive IDE for QTP and WinRunner.

While the automated testing performance is enhanced, the price is affordable. Here is a review of the Test Design Studio 2.0

Ease of use

Test Design Studio offers an intuitive interface wherein testers can enjoy a high-end VB IDE environment. The code navigation is made simple. You can categorize code into different segments, collapse and expand them as you desire. Using a top navigation bar, you can easily and quickly navigate to any piece of code. Otherwise, you have to scroll through multiple pages for a particular code. Moving between multiple QTP tests is easy and quick as well. In short, TDS offers the luxury of Visual Studio or Eclipse IDE.

The Performance

With an intuitive IDE, TDS offers a luxurious to easily work with large testing projects. The performance of TDS is ‘Good’.

The Price

You can download the evaluation version to check the functionality of the product. The evaluation version has all the features. At $1450 per single license, TDS comes with a decent price tag. However, when you run scripts, TDS automatically launches QTP. So, debugging tasks are again dependent on QTP and you have to purchase both licenses.

The post Review of Test Design Studio 2.0 appeared first on Automation Dojos.

WATIR stands for ‘Web Testing Application in Ruby‘. It is an OLE-based testing application that automates your browser using Ruby libraries. Here are some of the pros and cons of Watir in brief at first glance.

Functionality of Watir

Watir takes advantage of the built-in OLE capabilities of Ruby to automate browsers. Normally, HTTP-based tools create a browser simulator for a web-based testing system. Watir works in a different way wherein it takes the browser through the OLE protocol. By implementing the OLE protocol over Component Object Model (COM) architecture, Watir facilitates inter-process communication between the browser and Ruby. Dynamic object creation and manipulation is made possible as well.

For Internet Explorer, this process is called OLE Automation. The program that manipulates objects is called the automation controller. The automation objects are served by the Internet Explorer which is why it is called as the server. On the other hand, the Ruby program acts as a client to manipulate objects.

The post A Brief Review Of WATIR appeared first on Automation Dojos.

Over the years Functional Test Automation has come a long way from WinRunner to QTP and until ALM. The tools have evolved to a great extent in terms of enhanced functionality, look and feel and inclusion of support for new technologies, etc. The competition between some market-leading tools like Silk Test, and QTP including freeware communities like Selenium led to a great deal of innovation with versions after versions.

However, what I don’t feel has ever evolved is the precise ‘Definitions’ and distinctions between different kinds of Frameworks. There is a lack of clear understanding or documentation distinguishing between what we call frameworks. The online literature still talks about the same traditional or legacy definitions.

Well, this article is dedicated to the legacy definitions for some of the common Frameworks around QTP as we know them. This is the first post in the series while in the subsequent (coming soon) articles I will share our understanding and definition of Frameworks. So here is the traditional introduction to frameworks with a little preface …

Appreciate Frameworks

Before starting with automation, we should be defining a set of assumptions, rules and concepts that provides a framework within which we create our automation test suite. The framework is a foundation on which the physical structure of potential tests or test suite is based. This foundation itself could be comprised of more than one modular components (libraries or scripts) working together to provide for the test journey through AUT. The logical interactions among these components are again defined by Framework.

Defining a framework before starting an automation project keeps all the automation engineers aligned to common goals and objectives thereby less chance of failures and increased team efficiency. The advantages of laying a framework do not stop at the development phase but rather there are significant gains after the project completion.

A framework-based approach is proven to provide for increased code re-usage, higher portability, scalability to accommodate new tests, and less cost of maintenance. Such an approach also makes the automation robust, reusable, and easy to understand for new resources as well

In this tutorial, we will discuss various framework techniques and scenarios in which using the particular framework is productive. Below described are different types of Test Automation frameworks.

Types of Automation Framework

SystemUtil.Run "flight4a.exe","","","open"
Dialog("Login").WinEdit("Agent Name:").Set "Mercury"
Dialog("Login").WinEdit("Password:").Set "Mercury"
Dialog("Login").WinButton("OK").Click
Window("Flight Reservation").Check CheckPoint("Flight Reservation")

Call funcLoginApp
Call LoginApp

Public Function funcLoginApp()
SystemUtil.Run "flight4a.exe","","","open"
End Function

Public Function LoginApp()
              Dialog("Login").WinEdit("Agent Name:").Set "Mercury"
              Dialog("Login").WinEdit("Password:").Set "Mercury"
              Dialog("Login").WinButton("OK").Click
              Window("Flight Reservation").Check CheckPoint("Flight Reservation")
End Function

SystemUtil.Run "flight4a.exe","","","open"
Dialog("Login").WinEdit("Agent Name:").Set DataTable("Agent", dtLocalSheet)
Dialog("Login").WinEdit("Password:").Set DataTable("Pwd", dtLocalSheet)
Dialog("Login").WinButton("OK").Click
Check Flight Reservation Window has loaded

Advantages and Disadvantages of various types of frameworks

The post Traditional Framework Definitions (QTP) appeared first on Automation Dojos.

The growing web and mobile applications have posed several challenges for software QA teams. While usability and scalability are highly prioritized, compatibility across multiple channels and platforms is required to leverage available resources. Such a business scenario requires companies to run multi-channel testing procedures before releasing a product and this is where HP Borland Silk Test comes to your rescue.

With Silk Test’s latest offering, businesses can efficiently run a single test case or test suite on multiple interfaces ensuring that the application works seamlessly across channels, thereby providing swift development/testing to deliver higher performance at cost-effective expenses. This article provides a quick overview of Silk Test’s ‘Multi-Channel Testing’ and how it could leverage the test and cost benefits.

The Need for Multi-Channel Testing

Technology is moving away from desktops to web-based environments. The mobile revolution has brought in several smart end gadgets like tablets, iPads, and laptops. Applications that are designed for one interface need to run on multiple interfaces. Companies need to ensure that a single application is optimized for web browsers, mobile phones or tablets equally. With the advancement in technology, developers are optimizing codes to develop cost-effective projects. The same approach is required for a testing team. In a behaviour driven environment, user requirements remain the same while the interface changes. Test cases or scripts need to be reused to support multiple interfaces.

Challenges in Multi-Channel Testing

The traditional testing setup uses a hierarchical approach to software testing. Testing frameworks that use object-oriented programming is based on objects. Though workflow procedures might be the same, different GUI interfaces use different objects for receiving data. This is a big challenge for multi-channel testing environments. By using application-based frameworks, businesses can overcome this challenge. In an application-based framework, test cases are built for the application and GUI elements. Though it takes considerable effort to create these test cases, the same scripts can be used for multiple interfaces. This approach can reduce operational costs and save time as well. This is what multi-channel testing from HP Borland Silk Test offers exactly.

The post HP Borland’s Silk Test for Multi-Channel Testing appeared first on Automation Dojos.