Continuous Testing: Stepping beyond Automation Testing!

Today businesses are changing rapidly and they need to support rapid innovations and changes. Agility in responding to change is the key to success for every business. IT industries are adapting agile software delivery approach and one of the recent and most acknowledged such practice is DevOps. DevOps helps accelerate the TTM, reduce risks and provides continuous feedback. Continuous Testing is the most important and crucial aspect of DevOps which emphasises continuous process improvement.


Today we don't just need test automation. Times today demand a method which will help measure the risk of business failure, and not just a report which show if tests have passed or failed. This impacts not just changes (or upgrades) in technology and tools, but also a change in quality management culture is observed.


Test automation helps us test faster, and provides a mechanism to detect software defects. Though automation can be considered as a pre requisite to continuous testing, continuous testing is much more. It helps provide process improvements that can prevent future defects from occurring. It plays an important role in providing continuous feedback for your software.



Outline/Structure of the Talk

This session will talk about what is Continuous Testing, why it is important and how it is changing the software delivery pipeline.

It will showcase a case study of how Docker can be used for Continuous testing.

Learning Outcome

Understand that:
- CT is taking the automation concepts beyond running tests using scripts.
- CT resets the question from “are you done testing?” to “is the level of risk understood and accepted?”
- CT is bringing about a cultural change. Software quality is now measured not by a separate QA team. It is becoming an integral part of the software delivery pipeline.
- An insight into the technical know how of how continuous testing can be achieved

Target Audience


schedule Submitted 3 years ago

Public Feedback

comment Suggest improvements to the Speaker
  • Schalk Cronjé
    By Schalk Cronjé  ~  3 years ago
    reply Reply

    The feeling I get from reviewing the slides is that it focuses more on deployment, rather than continuous testing. I would prefer a session like this to focus on how Docker aids in automated testing also showing some practical examplea. If a presenter is prepared it is possible to do a live demo of Docker without having to download anything again over slow conference wi-fi.


    For instance if MySql is needed in testing how can you spin an instance up with Docker run the tests and tear it down again. How can you automated locallised testing (i.e. on developer machine) and in CI with Docker.


    I think if you can reowrk your submission to be like that if would be good. (The last thing I want is for people to fall asleep in  a sesison due to a lot of theory).

    • Mukta
      By Mukta  ~  3 years ago
      reply Reply

      Thanks for reviewing the proposal and for your comments. Your point is noted. 

      The slides shared are for ref, they presented at another conf. For this conference I am planning to redo the entire deck. Practical application of using docker for continuous testing can be demoed.

      Thanks for your suggestions, I will update the course outline soon.

  • Liked Mukta

    Mukta - Using Docker for Testing

    schedule 3 years ago
    Sold Out!
    45 Mins

    The early release of Docker (while it was in beta) was primarily used for testing. It was immediately accepted as the best tool which facilitated automation testing. Docker and its ecosystem have matured today to also support Docker in production.

    Tests typically include a number of different components like DB Server, App Server, Web server. Tests also depend on external services like MySQL, Redis. Moreover, the engineers are not very conversant with the testing infrastructure: A QA engineer should ideally focus on writing and executing tests. Failed tests pollute the test environment and resetting it back to a clean test environment is an overhead. Using Docker can address all these issues.

    This session aims to show how Docker can be effectively used in manual and automation testing. It will demonstrate how Docker can be used in CI + automation testing, which can form the base for your "continuous testing" approach.

  • Liked Sargis Sargsyan

    Sargis Sargsyan - Better Page Object Handling with Loadable Component Pattern

    45 Mins

    One of the painful problems in Selenium automated testing is determining whether a HTML page has been loaded. This is especially the case when web application uses a JS  heavy framework such as the popular AngularJS.

    During this talk we will discuss how to handle Selenium Page Object pattern better with Loadable Component.

    The Loadable Component helps test case developers make sure that the page or a component of the page is loaded successfully. I will share my experience about the concept of the Loadable Component and Page Object patterns.

  • Liked Priti Biyani

    Priti Biyani - One page to test them all!

    Priti Biyani
    Priti Biyani
    schedule 3 years ago
    Sold Out!
    45 Mins
    Case Study

    Problem we faced

    Our current project is a mobile app for iOS, Android and Mobile web, which is a mixture of pure native screens and webviews. Each platform has its own tools for UI automation like Calabash for iOS/Android and Watir-Webdriver for Mobile Web. But we wanted to create a generic automation framework which could support each of the  above UI automation frameworks but still reuse as much code as possible and avoid duplicating code between them.


    Page Object Model

    Page Object  Model was again a natural fit for this framework. Most implementations of POM recommend different POMs for each platform. But we wanted to have a single Page Object Model for all the 3 platforms to ensure maximum code reuse and reduce overall time spent in adding new automation.


    Single Page Object Model across platforms

    This was complicated because we had native screens as well as webview screens and so it was not possible to use the same Page Object. To solve this, we introduced abstractions for the elements on the screen and encapsulated the respective native driver implementations.

    This also allowed us to implement common automation tasks in one place for e.g waiting for new pages to load, so that this code is not repeated across multiple step definitions and platforms. This helped us move to thinking in higher domain level concepts than in terms of low level UI interactions.

  • Liked Prateek Yadav

    Prateek Yadav / Nirmal Jacob / Sanjay Kulkarni - Automation testing approach for Responsive web Design website

    20 Mins

    In the market today, there are a large number of devices with different resolutions and screen sizes. A tough competition exists wherein every client wants their website to run on all these devices.

    Testing the same set of test cases on all the available devices in the market today is practically impossible due to the high cost factor, availability of all devices and amount of effort required to test on all these devices. Now a days, most of the websites are being developed as Responsive web design(RWD) websites. The RWD websites layout will adjust based on the screen size and PPI of the device. The main challenge for testing RWD websites is that the automation script generated for one device one platform will only cover the functionality, behavior and workflow. But the same automation script running on different devices ignores the  look and feel, Layout and UI alignment.


    This Paper talks about using multiple tools available in the market currently for testing RWD website and our experiences related to them. We have focused majorly  on screenshot analysis and pixel by pixel comparison. We also have capability to execute parallel test cases for RWD website across multiple devices having multiple resolutions in one go along with continuous integration using Selenium and Jenkins.

  • Liked sriharsha Narayanam

    sriharsha Narayanam / Anish Cheriyan - Penetration Test Engineering - A Systematic Approach

    45 Mins
    Experience Report

    Penetration Testing is an important activity and ability to do the penetration testing effectively should not be limited to few senior security professional in an organization.

    In our presentation , we will bring the systematic Engineering approach to Penetration Testing , such that it is not left for a chance.

    We will touch upon the Security Principles and Threat modeling which are foundation for a secure product

    Also we will present a success case of the application of this Engineering practice in our organization 

    High level topics list that will be discussed are as below.

    • Introduction

    • Principles of Security for Secure Products

    • Security in Product Development Life Cycle

    • Threat Modelling

    • Secure Coding

    • Penetration Test Engineering analysis 

    • Cyber Security- a mindset and some anti-patterns

    • Conclusion

  • Liked Ashish Mishra

    Ashish Mishra - Data driven testing using Appium, Cucumber and FitNesse

    45 Mins

    My topic will have demonstration of running Mobile test automation using FitNesse and Cucumber tools. Agility will be driven using test-first approach such as BDD and ATDD with data driven testing.