I want the site to be tested on Firefox, Chrome, Safari and yes, even IE 11. To add, the site should be responsive and should support mobile and tablet resolutions too. How often do you see this being listed in a Test plan? Almost, all the websites need to supported on multiple browsers and devices, right? Just imagine the manual effort required here. To add, the site is multi-linguistic. Wow, that just doubled all your manual efforts! How about if we automated the visual regression tests too, just the way functional regression tests are? Sounds great, isn't it?

Once you agree with the above paragraph, allow me to explain the concept of automated Visual regression testing, how the visual tools work in general, the concepts around it and the benefits of using them, along with the challenges faced during actual implementation of the tests. There are a couple of tools available in the market, using which you can directly get started with automating your visual tests too.

Even if you have a large QA team, identifying CSS issues on multiple browsers and devices with every build can become a tedious job, erroneous since once cannot capture small pixel differences or even similar color related issues. Therefore, automating them is soon going to be a must have in every Test Plan.


Outline/Structure of the Talk

  1. Why is automated Visual regression testing needed?
    1. Difficult to spot
    2. Time consuming
    3. Support for responsive tests
    4. Repetitive task
  2. How does it work?
    1. Capture screen-shots
    2. Create baselines
    3. Comparison
    4. Generate output
  3. Introduction to Wraith tool
    1. Installation
    2. Testing modes
    3. Demonstration using Wraith tool
  4. Brush through Advanced concepts
    1. Test interactive content
    2. Support for various actual browsers and devices
    3. Continuous Integration
    4. Who should use it?

Learning Outcome

Come, participate and learn about:

  • Need for automated Visual regression tests
  • How do these tools function in common
  • Various tools available in the market
  • How to get started with the tests using Wraith
  • Advanced stuff on how to handle interactive content

Target Audience

Front-end engineers, QA engineers, Test Engineers

Prerequisites for Attendees

No prerequisite


schedule Submitted 5 years ago

  • Shweta Sharma

    Shweta Sharma / Mohit Aghera - Behat - Arguably the best PHP tool to switch to Automated testing from Manual

    45 Mins

    In no time, the term 'Manual QA" is going to be a dinosaur. What does that mean? Are all the Manual QA going to extinct? Thank Behat, Manual testers can have a bright career into Automation. The term automation is itself horrifying, which means complex framework, complex setup and the biggest of all, lots and lots of coding involved.

    Behat is an open source BDD PHP framework. It has a rich library of extensions which will help you test user workflow and interact with the Web application using Mink, test your APIs and also develop a Page Object Automation framework.

  • Kushan Amarasiri

    Kushan Amarasiri - Unleash the Power of Selenide ~ Developing an End to End Automation Framework with Selenide

    480 Mins

    Selenide is a wrapper automation tool which uses Selenium WebDriver. It has many advantages compared to traditional WebDriver. Selenide supports AngularJS web solutions and it has also helped to reduce the most of the commands that we use for Traditional Selenium Automation tool. Selenide has been used widely in the industry and its free and open source test automation tools used widely among test automation professionals. In this workshop session I would be disseminating my knowledge to the audience about the Selenide Tool, Integrating Behavior Driven Development, Integrating Interactive Reporting Dashboard, Integrating Configurability and Promoting Reusability via Page Object Model. This session would be a highly interactive session where the audience will be given hands on practice on how to create a test automation framework using Selenide. This workshop will be done by Taking a practical and realistic test automation scenario.

  • Shweta Sharma

    Shweta Sharma / Mohit Aghera - Automated testing using Behat and Selenium

    480 Mins

    Do you want to deliver a well-tested website, covering all the test scenarios in every iteration? Excellent, then what is the problem? Oh, too much of manual effort in executing the regression test cases. Well, then automate it. Now, what? Automation, huh, it needs a lot of coding, too much of investment. OK, enough reasons given, the list can go on.

    Get started right on with automating your test scenarios with minimal code is what all Behat is about. Behat proved to be extremely useful to me in order to enter the world of automation. After understanding the architecture and its correct usage, my team and me could automate around 70% of the test cases by writing no/minimal PHP code. The lovely features provided by Selenium Webdriver can be easily integrated into Behat with the help of Selenium2Driver which comes out of the box. It is an automation testing framework, coupled with rich libraries in the form of extensions to enable users automate their acceptance tests, API tests and even create a Page Object model when needed. You can execute tests on various browsers or even headless browsers like phantomJS and headless Chrome for faster execution.

    Since Behat is built on the lines of Cucumber and promotes BDD, it has proved to be an extremely useful tool to ensure that were are first building the right system followed by the system is being built right. With the help of human readable scenarios written in the feature files, the automation system can be understood by all the three parties - Business people, developers and testers. Gherkin language enables the tester to build more and more strong and a rich Automation test suite than trying to get the code right. composer.json and behat.yml files enable the user to configure stuff in no time.

  • Nalilnikanth Meesala

    Nalilnikanth Meesala / Prasad Mudedla - Continuous Security with Selenium tests

    45 Mins

    We have come to a place where we run our selenium tests on pipelines every day.
    Now are these tests confined to test only the functionality of the application?
    No, we can use this tests to do much more. Let's test security with those same tests.

    Turn your selenium tests in to Security tests, get security testing in to your CI pipelines just by tweaking a bit of the selenium integration suite. Find and report security issues that exists which can be caught way before paying off for it.
    In this Demo we will introduce a framework that will help your selenium tests turn into security tests and run on pipelines.
    With ZAP API + selenium and CI pipelines, find security issues on the application see a red or green security pipeline. Not just that fetch the reports and take necessary actions on every build.
    The talk covers different ways that ZAP tests the web application for security(automated with selenium tests). We will see what all of them can be integrated with selenium and can make most out the suite.
    As an add we will see how your API can be tested for security using ZAP API :)

    Tools used:
    1. Selenium Web driver framework.
    2. ZAP framework integrated with selenium framework.
    3. GO (for CI/CD)
    4. Maven for building and fetching reports.