With frequent time boxed releases and flexible requirements in agile teams, test automation faces numerous challenges. The most frequent issues being too much to automate and never enough time, automation lagging behind, flaky scripts that need too much maintenance and lack of skill, time & resources. Haven’t we all asked what to automate and how to go about the daily tasks with the automation cloud looming over our heads. Here we’ll discuss answers to some of these questions and try to outline a number of approaches that agile teams can take in their selection of what to automate, how to go about their automation and whom to involve, and when to schedule these tasks so that the releases are debt free and of best quality.

What to Automate –> Regression averse approach | Selective approach | Sanity Automation | Max automation approach

When to Automate –> End-of-Release | Sprint n-1 approach | Continuous automation

How to Automate –> All hands approach | Shared Automation expert | Code-averse tool

Understanding these possibilities, you can pick the right combination to form your own test automation strategies. Let us have a look at an integration of these possibilities, the possible combinations and what may or may not work!


Learning Outcome

  • Learn the different possible approaches you can take for What, When and How to automate
  • Understand each approach, its flow of work and a tester’s contribution
  • How to create a robust test automation strategy using a combination of these approaches
  • See which potential combinations may or may not work!

Target Audience

Testers, Test Automation Engineers, Test Managers, Agile Team Leads, Scrum Masters

schedule Submitted 10 months ago

Public Feedback

    • Jeremias Rößler

      Jeremias Rößler - recheck and the Sorcerer's Stone: Turning Selenium into Adamantium

      45 Mins

      Ever had that: after a simple change, suddenly 50+ tests are failing! Brittle tests that hinge on GUI specifics and result in the dreaded NoSuchElementException are a main headache when testing with Selenium.

      The open source project recheck offers a simple and elegant solution. Not only is a virtual identifier unaffected by UI changes, you can define it for otherwise hard to specify elements, i.e. that would require complex xpath or CSS selector expressions. And on top of that, tests are easier to create and maintain and yet much more complete in what they check. This talk gives a practical introduction to the underlying approach and the tool, complete with a life coding session.

    • Parveen Khan

      Parveen Khan - Exploring a DevOps Transformation Like a Tester

      45 Mins

      Just when we, as testers, got a handle on what Agile means for us, the landscape changed yet again to a DevOps culture. Words like continuous integration (CI), continuous deployment (CD), and pipelines are now ones we’re hearing on a daily basis. As a tester, I’ll admit, I had no clue of what these words meant, and how was I to change the way I tested to fit within this DevOps culture.

      Researching about DevOps provided some information, but it was still fuzzy how testing fits into this process. As opposed to panicking about yet another shift in culture, I decided to approach this with a tester’s mindset and explore it just as I would a new application.

      In this talk, I’ll share my journey of how illustrating models to visualize and understand CI/CD pipelines helped me; my various phases of exploration of the DevOps culture; and the thoughtful questions that I posed at each phase to learn more about this methodology. I’ll also share how my new understanding of DevOps influenced my decisions on which automated tests should be contributed to the CI/CD pipeline and at which stages.

    • Sri Harsha

      Sri Harsha - Memory Leaks: The silent thieves in Web Application

      Sri Harsha
      Sri Harsha
      schedule 11 months ago
      Sold Out!
      20 Mins

      We’ll love browsing, it may be your blogs, visiting your pages, searching for a content and it may be an application you developed. So, have you ever observed issues like slowness in web-application while browsing, reduce in page performance over time, application quit unexpectedly, and devices stop working? And no wonder every new web technology in this era faces this issue and these applications are victim of memory leaks?

      In a world of automated system, everything is automatically managed under browser hood for a web application. Asynchronous operations, Executing instructions, Automatic garbage collection etc. But even after effective management of operations in a complex program, there is a small amount of failures happens in disposing the memory used and those are difficult to debug because they are not the application features.

      So, it is important for every web developer/tester sitting out there to understand/visualize the importance of memory leaks in an application, Because at the end we’re the one responsible to make the application to be alive