location_city Virtual Platform schedule Sep 12th 11:30 AM - 12:15 PM place Online Meeting 1 people 36 Interested

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

I would be talking about the following topics:

  • What is Automated Visual testing?

  • Is there a need to automate visual tests? Why?

  • How does the basic algorithm work for any tool supporting automated visual tests? Demonstration on:

    • Create a test

    • Execute a test

    • Interpret the results of a test

  • Challenges with automating Visual tests

    • Anti-aliasing

    • Dynamic Content

    • False positives

  • Can the above challenges be addressed?

    • Are there any open source/commercial tools available to address these challenges?

    • Demonstration - How do they address them?

  • What should be the strategy to design and execute the Automated Visual Test Suite?

    • Capturing screenshots for - Full page, element, viewport

    • Is it necessary to execute each and every test on your browser/device matrix?

    • Demonstration - Can we organize our Test Suites to optimize the execution?

  • Challenges faced and potential solutions for introducing Automated Visual testing in your CI/CD pipeline

  • A quick comparison of tools available in the market - Use what when?

  • How to get started with this type of Automated testing?

    • No coding knowledge/experience - Don't worry, there are config-based, record and playback tools available

    • Good coding knowledge/experience - Wonderful, leverage your skills to address the challenges

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 advantages of using it?

  • What are the challenges associated with it and potential solutions?

  • What are the good practices associated?

  • What are the tools available in the market?

  • When to use what?

  • How can you get started 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 11 months ago

Public Feedback


    • Anne-Marie Charrett
      keyboard_arrow_down

      Anne-Marie Charrett - 2020 Vision:: Leadership

      45 Mins
      Keynote
      Intermediate

      It’s 2020 and a new decade awaits us. 100 years ago, our world was famous for the Russian Revolution and World War 1.

      In our century, we are also facing tremendous upheaval. The bushfires in Australia, floods in Indonesia. We are seeing the impact of climate change before our eyes.

      Technology-wise, agile has become mainstream. Hardware is cheap, CI and CD are commonplace. Robotics and Machine Learning is a reality. This is the age we live in. This is the now.

      How do we begin to plan for such a reality? How do we test software in such an ecosystem? Should we even try? How do we maintain skills, when frameworks change as rapidly as nail varnish on a teenager?

      As leaders in software testing, these are the questions we need to be able to answer. We need leadership now more than ever. We can’t predict the future, but we can prepare ourselves to be able to deal with change, to develop strategies that facilitate rapid learning and rapid change.

      We can upskill our people to be able to handle inconsistency and complexity. To know when technology is beneficial and when to rely on our ability to think critically.

      We must create environments where talent can grow and thrive. We learning (and failure) are embraced. Today is the day, we become the test leaders of the future. Are you with me?

    • Shweta Sharma
      keyboard_arrow_down

      Shweta Sharma / Nikita Jain - Accessibility testing 101

      45 Mins
      Talk
      Beginner

      "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.