In this era of Digital transformation, clients have been demanding shorter and quicker releases. Shorter and quicker releases mean your team should not only be able to develop them at the required pace but also test and release them at a sustainable pace. User interface plays an important role in the client's business and there are organizations that release new features, fancy CSS regularly that support multiple browsers, multiple Operating systems, mobile devices. Verifying the frontend on this browser/device/OS matrix by humans is not only extremely time consuming but also prone to human errors. In fact, testing by humans should primarily focus on discovery leaving the repetitive and error-prone tasks to tools. Hence, automating Visual tests is becoming less of an optional activity and more of a must-have activity within the team. Ensuring visually perfect user experiences is equally important as to have the functionality working.


Outline/Structure of the Talk

Apart from brushing through the concept that revolves around Automated Visual testing, I would be talking about the following topics:

  • How to get started with it?

  • A quick comparison of tools available - Use what when

  • Challenges with automating Visual tests

  • Demo using Visual regression service by WebdriverIO

    • Parallel execution on multiple browsers

    • Support for tests using Mocha, Jasmine and Cucumber framework

    • Organizing Test Suites

    • Report generation

    • Run tests on Cloud

  • Demo using Applitools
    • Browser extensions

    • SDKs

Learning Outcome

At the end of the session, attendees will learn about:

  • What is Automated Visual regression testing?
  • How does it work?
  • What are the tools available in the market?
  • When to use what?
  • How can you get started with it?
  • What are the advantages of using it?
  • What are the challenges associated with it?
  • Introducing Visual automation in your CI cycle

Target Audience

QA / Test Automation engineers who want to reduce the time spent on testing on various devices and browsers, Front end developers who want to ensure that new changes don't introduce regression before they push their code and Project Managers who want to introduce this technique in their organization

Prerequisites for Attendees

There are no prerequisites for this session.

schedule Submitted 1 week ago

Public Feedback

comment Suggest improvements to the Speaker

  • Liked Shweta Sharma

    Shweta Sharma / Nikita Jain - Accessibility testing 101

    45 Mins

    "This world is such a beautiful place to live in." If you can read the first sentence without any screen readers or assistance, you're privileged. As technologists, shouldn’t we be more empathetic towards differently-abled people and make all parts of our website accessible to them? In my humble opinion, the true power of technology can be identified when it reaches out to people of all kinds having different physical or psychological challenges. We not only legally bound to provide Accessibility but also it should be considered as our moral responsibility.

    As testers, we have a wonderful opportunity to contribute to Accessibility by ensuring that the site is accessible in many different ways. Although it is impossible to identify all the issues that exist around Accessibility in the world, we are lucky enough to still understand a majority of them. With this understanding, there have been many measures taken in order to make your site accessible. But, don’t forget - we are QA engineers. We got to ensure that the site is accessible as per the standards set by WCAG 2.0 (AA) by testing for accessibility using various tools and techniques.