Accelerate CI/CD Pipeline Blog Series – Part II – Test Automation

In part I of this blog series we spoke about Continuous Testing (CT), CI CD and that Test Automation is a key to its success, how to leverage test automation to enable coverage and speed. Let’s get an in-depth understanding of why it’s essential.

Why Automation of Testing is Essential for CI CD

Code analysis tools, API testing tools, API contract testing tools, Service virtualization tools, performance assessment tools, and end-to-end automation tools are all parts of CT. However, test automation is one of the key enablers of CT as:

  • It allows us to execute tests in parallel, across multiple servers/containers, speeding up the testing process.
  • It frees engineers from repetitive tasks, enabling them to focus on value-adds.
  • It helps validate the impact of even minor changes continuously.

Characteristics of a Good Automation Framework

For test automation to be effective, it must be supported by efficient frameworks. The frameworks provide a structure and help integrate and realize the efforts of a distributed team.

  • Test frameworks must support various languages, browsers, and techniques to make them future-proof. They must possess an Agile testing environment to support the continuous delivery pipeline.
  • The testing platform must be scalable to support as many tests as needed.
  • The platform must support compatibility tests on simulated devices to cut down the cycle.
  • The environment should maximize automation, i.e., trigger tests, analyze results, and share test information across the organization, in a fully automated manner.
  • The testing platform must include security features such as encryption of test data and access control policies

Characteristics of Trigent’s AutoMate Test Automation Framework

Reinforced by globally renowned partners, Trigent’s testing focus is aligned with the current business environment and offers cost benefits, performance, and agility.

As niche test automation experts, we have significant experience in open source and commercial testing tools. Our extensive library of modular, reusable, and resilient frameworks simplifies scenario-based automation. We provide on-demand testing and next-gen scheduling.

Features and benefits
  • Accelerated script development: Script/test cases development effort reduced up to 60-80% in comparison to traditional test automation approaches. Reduces Test Scripting Complexity.
  • Modular and reusable framework components: Reduced dependency on tool-specific resources. Ability to kick-start automation quickly. It supports reusable components. Reduced Test Automation maintenance costs. Allows multi-browser, multi-device testing.
  • Easy test script maintenance: Ease of test execution. Easy to make changes and maintain scripts in the long run. Improved error and exception handling. Supports multiple scripting languages.
  • On-demand Testing: Sanity, Smoke, Integration, Regression, etc. Provides effective test data creation on the go.
  • Hybrid Model: Modular test framework built using JUnit or TestNG. Integrates with multiple test automation tools. Allows a common way of handling multiple test types.
  • Scheduling and customized reporting: Send test results to ALM. Integrates with Test Management tools to track your test plans effectively.
  • Leverages new tech trends: Leverages AI/ML utilities & tools that allow for effective Test Impact analysis and test selection. Integrates with CI/CD tools to enable automated executions. Allows parallel executions to reduce test execution time

Learn more about Trigent software testing services or test automation services

Accelerate CI/CD Pipeline Blog Series – Part 1- Continuous Testing

Given its usefulness in software development, Agile methodologies have come to be embraced across the IT ecosystem to streamline processes, improve feedback, and accelerate innovation.

Organizations now see DevOps as the next wave after Agile that enables Continuous Integration and Continuous Delivery (CI/CD).  While Agile helped streamline and automate the entire software delivery lifecycle, CI/CD goes further. CI checks the code often, and the tested chunks are integrated, sometimes several times in a single day, to create a stream of smaller and frequent releases through CD.

As a principal analyst at Forrester Research puts it succinctly: ”If Agile was the opening act, continuous delivery is the headliner. The link that enables CI/CD, however, is Continuous Testing (CT).

What is Continuous Testing?

Continuous Testing is a process by which feedback on business risks of a software release is acquired as rapidly as possible. It helps in early risk identification & incremental coverage as it’s integrated into the delivery pipeline. Continuous Testing is achieved by making test automation an integral part of the software delivery pipeline. It’s seamlessly interwoven into the software delivery pipeline (not tagged at the end).

Though CI/CD enables speed-to-market, inadequate end-to-end experience testing can turn it into a liability.  A key aspect of CT is to leverage test automation to enable coverage and speed.

Test Automation – Continuous Testing’s Secret Success Factor

Automation of tests is the key to ensure that Quality Assurance is as continuous, agile, and reliable.  CT involves automating the tests and running them early and often.  It leverages service virtualization to increase the test coverage when parts of the business functions are available at different points in time.

Automated Testing binds together all the other processes that comprise the CD pipeline and makes DevOps work. By validating changing scenarios, Smart automation helps in faster software delivery.

In part II of the blog series we will talk more about why test automation is essential for CI/CD Testing, and automation framework.

Learn more about Trigent software testing services or test automation services

Cucumber Test Automation Framework


Cucumber is a testing framework that helps to bridge the gap between software developers and business managers. Tests are written in plain language, based on the Behavior Driven Development (BDD) style of Given, When, Then, which anyone can understand. It is defined by a Language called “Gherkin”

Difference between TDD and BDD:

TDD: TDD (Test Driven Development) is an iterative development process. Each iteration starts with a set of tests written for a new piece of functionality.

BDD: BDD (Behavior Driven Development) is a synthesis and refinement of practices stemming from TDD. Like in TDD, in BDD also, we write tests first and then add application code.

The main objective of this automation framework is to provide the test script development environment, which is BDD based.

The major differences that we get to see here are:

  • Tests are written in plain descriptive English type grammar.
  • Tests are explained as the behavior of the application and are more user-focused.
  • Using examples to clarify requirements.


  • Install JDK and Eclipse on your machine
  • Install Cucumber in Eclipse.
  • Add J Unit to “build-path” in Eclipse.
  • Add Web Driver jar files to “build-path” in Eclipse.

What is “Gherkin”?

Gherkin is a simple, lightweight, and structured language that uses regular spoken language to describe requirements and scenarios.

Gherkin Keywords:

  • Feature: Each Gherkin file begins with a ”Feature” keyword. Feature defines the logical test functionality you will test in this feature file. e.g. if you are testing a “payment gateway”, your Feature will become “Payment Gateway”.
  • Scenario: Each Feature will contain some tests to test the feature. Each test is called a Scenario and is described using the Scenario keyword.
  • Given: Defines a “precondition” to the test.
  • When: This keyword defines the test activities that will be executed. By test action, we mean the user input action.
  • Then: This keyword defines the outcome of previous steps.
  • And: This keyword is used to add conditions to your steps.
  • But: This keyword is used to add negative type comments.
  • *: This keyword is very special. It defines the whole purpose of having Given When Then and all the other keywords.


Feature: Login Action Test
Description: This feature will test a Login and Logout functionality

Scenario 1:

Unsuccessful Login with Invalid Credentials

  1. Given User is on Homepage
  2. When User Navigate to Login Page
  3. And User enters Username and Password
  4. But The user credentials are wrong
  5. Then Message displayed Wrong Username & Password

Scenario 2: 

Successful Login with Valid Credentials

  1. Given User is on Homepage
  2. When User Navigate to Login Page
  3. And User enters Username and Password
  4. Then Message displayed Log in Successfully


  1. We need to write the “Step definition” in a java class for each and every behavior written in the ‘.feature’ file.
  2. All the web elements are declared in a Class( under “com.cucumber.commonlibs” package.
  3. All the constants are declared in a Class( under “com.cucumber.stepdefinition” package.
  4. The trigger of execution is declared in a Class( under “com.cucumber.stepdefinition” package.

Step Definition:

  • A Step Definition is a small piece of code with a pattern attached to it.
  • In other words, a Step Definition is a java method in a class with an annotation above it. An annotation followed by the pattern is used to link the Step Definition to all the matching Steps.
  • Cucumber finds the “Step Definition” file, with the help of Glue code in Cucumber Options.


@Then("^Message displayed Login Successfully$")
 public void message_displayed_Login_Successfully() throws Throwable {
 System.out.println("Login Successfully");


  • “Mail notification” enabled, on failure of build.
  • “Scheduled execution” can be performed.
  • Captures the “screen shots” promptly, on failure and embeds with the report.
  • Supports to run the execution, individual/suite wise.
  • OS independent and Browser independent.
  • Easy to understand.
  • Easy to use, highly flexible and above all “Free of Cost”.
  • Provides “micro-reporting”, with the statistics of passed, failed, pending, skipped, undefined and missing steps.

Power your next-gen software products through our automation testing services. Learn from our experts.

Exit mobile version