Software World has always been obsessed with delivery speed , value and outcomes but one thing that covid pandemic has taught us in last 2 years is to focus on "safety first" 

But Why? 

• Increasing cyber threats & attacks - In 2021 cyber attack incident occured every 11 seconds ,this is twice the rate of 2019 and four times of 2016

• Rising cost of vulnerabilities - cyberthreats/Crime industry is costing $6 trillion annually in 2021 and reaching $10.5 trillion in 2025 making it the world’s third-largest economy, after the United States and China.

• Increasing penetration and demand  - Organisations are compelled to deliver changes so swiftly that the security don’t get enough time to catch up, leaving businesses vulnerable to the threats looming across the horizon.

So what does safety means in context to software and how can we enable this across our development life cycle in continuous way ? 

In this Talk we will present approach for implementing automated security at every phase of SDLC for the tooling aspect and practices for setting up DevSecOps in your Organisation.

We will focus on leveraging existing automation tools like selenium, appium and infrastructure as much as possible for everyone to get these implemented with minimal time, cost and learning curve.

We all have read or heard about test automation pyramid .But is it really supposed to be a pyramid ? or it's just a metaphor? lets find out

At this talk we will share our learnings from implementing test automation pyramid for years and its variations finally arriving to test automation cup modal focusing on

1.Need for growing up from automation testing pyramid

2.How the modern testing stack has evolved

3.How to choose and design your automation testing stack

4.Real World examples from testing to validate our test cup model

5.How to move from Pyramid to test cup and Our lessons learned

6.Sharing Best practices ,limitations and patterns for success

We love to continuously test our websites and apps on real browsers like chrome, firefox and over desktops and mobile devices.But what if you want to run your tests on any device where there is no display especially as part of large CI/CD pipeline.

The best and easiest but least followed approach is to use a headless Environment.

A Headless Environment is a device or a web browser without a graphical user interface, controlled programmatically and generally used for testing and common automation purposes like taking screenshots, scraping websites etc.

At this talk we will learn how to leverage the headless browsers and devices to solve the challenges of growing testing infrastructure and continuous delivery with key focus on below items.

• Basics of the headless browsers and devices and specifically it’s application on the test automation.
• How Headless Tests can reduce the time of test execution, ease the setup of clean test environments and drastically reduce the differences between the development, acceptance and production environments leading to the higher quality of the released software.
• Examples to run both web and mobile (android)UI tests headlessly with major automation tools like selenium and appium.
• Integrating and managing headless tests to optimize continuous delivery pipeline.
• Sharing Best practices and patterns for success with headless environments from our experience of using it for more than a year.

Recently DevOps movement has given rise to a need to maintain visibility across the teams.How will your testing team keep pace with this change in future?

Chat based Testing is basically extending ChatOps to testing that will keeps the people involved in software development more connected and facilitates conversation-driven development.
It allows you to aggregate information about processes, discussions, QA, and testing. This flow improves the delivery of information about the status of the project to all members of the team.Also It allows to present, demonstrate, and reproduce an issue to the other teams.
which can be fixed before they reach users or customers—with minimal disruption to the delivery pipeline.

Imagine what if everything is automated , now what ?  are you done yet ?  

No , We still want our team's deliverables to be clean and unambiguous, reducing friction in our delivery pipeline , but how is this possible forever ?

Solution - Container contracts to facilitate clean deliverables between teams.

A Container contract is a clean line of separation between teams, where the Docker image is both the borderline and the unit of exchange.

We see two upcoming trends in the world of software delivery.

1.Docker is becoming a standard for managing infrastructure using containers.

2.Testing code and its infrastructure starts to grow at scale with more complexity, dependencies and technology diversity.

A container is an entire portable runtime environment: an application, plus all its dependencies, libraries and other binaries, and configuration files needed to run it, bundled into one package. By containerizing the application platform and its dependencies ,all differences in OS distributions and underlying infrastructure are abstracted away which makes it easy to share and execute anywhere.

At this talk we will learn how to leverage the container technology to solve the challenges of growing testing infrastructure and continuous delivery with key focus on below items.

• Basics of the containers technology and specifically it’s application on the test automation. 
• How Docker can reduce the time of test execution, ease the setup of clean test environments and drastically reduce the differences between the development, acceptance and production environments leading to the higher quality of the released software.
• Examples to containerize entire testing stack together consisting of major automation tools (selenium, appium, phantomjs), performance tools (jmeter,gatling) with cucumber. 
• Integrating and managing testing container with other application containers to achieve easily manageable continuous delivery pipeline.
• Best practices and patterns for docker success.

We see two upcoming trends in the world of software delivery.

1.Docker is becoming a standard for managing infrastructure using containers.

2.Testing code and its infrastructure starts to grow at scale with more complexity, dependencies and technology diversity.

A container is an entire portable runtime environment: an application, plus all its dependencies, libraries and other binaries, and configuration files needed to run it, bundled into one package. By containerizing the application platform and its dependencies ,all differences in OS distributions and underlying infrastructure are abstracted away which makes it easy to share and execute anywhere.

At this talk we will learn how to leverage the container technology to solve the challenges of growing testing infrastructure and continuous delivery with key focus on below items.

• Basics of the containers technology and specifically it’s application on the test automation. 
• How Docker can reduce the time of test execution, ease the setup of clean test environments and drastically reduce the differences between the development, acceptance and production environments leading to the higher quality of the released software.
• Examples to containerize entire testing stack together consisting of major automation tools (selenium, appium, phantomjs), performance tools (jmeter,gatling) with cucumber. 
• Integrating and managing testing container with other application containers to achieve easily manageable continuous delivery pipeline.
• Best practices and patterns for docker success.