Are ALL of the below statements true regarding your functional automated tests?

• As a result of your functional automation, manual testing efforts are reduced.
• Automated tests run fast.
• Automated tests are triggered automatically on any product change.
• Automated tests can run, on-demand, on different (supported) browsers/devices without making any changes in code or configuration.
• The automated test execution needs no manual intervention to run/complete successfully.
• Your automated functional tests give deterministic feedback - i.e. no flaky/intermittent test failures.
• You have all the relevant information to do RCA of failed tests readily available.
• Consolidated reports and trends from test runs are available in a central reporting server for the team.
• The automated test code is clean and easy to maintain, reuse and scale.
• Your automated tests can run in any order, and in parallel.

If you have answered yes to all the above statements, you would be in the very small percentage of teams doing functional automation right!

In my experience, I have seen teams struggle with more than one, and in many cases, all of the above statements. 

On retrospection, I have realized, that most of these challenges are because of a combination of the following issues:

• Lack of holistic vision, understanding, skills, and capabilities for taking on this seemingly easy activity of functional test automation
• Lack of time for design, implementation, and maintenance of the automated test code

In this session, I will share, with examples, the features & capabilities that are not used right in Test Automation implementation resulting in you answering “NO” to the above statements. These are anti-patterns of functional automation implementation and have a negative impact on the quality of feedback from your automated tests.

More importantly, I will share approaches and solutions of how you can avoid these anti-patterns and evolve to answer “YES” to each of the above statements.

CI With Bazel (Why Selenium is Using It and You Should Too)

Welcome Address and Selenium Conf Overview. Here you will get al the important details you need about the conference. So don't miss it.

Dan Cuellar was selected to speak at Selenium Conference 2012 in London about an entirely different topic. As part of his presentation, he showed off iOS Automation using Selenium syntax to demonstrate writing platform-agnostic tests that use separate platform-specific page objects with a common interface. To his surprise, the cool test architecture would take a backseat to the spectacle of iOS tests running like WebDriver tests. Several people suggested that he give a lightning talk later in the conference to explain exactly how it worked.

On the second day of the conference, Dan stepped up on stage to give the lightning talk. Jason Huggins, co-creator of Selenium, moderated the lightning talks. Dan experienced technical difficulties getting his presentation to load, and Jason nearly had to move on to the next lightning talk. At the last moment, the screen turned on and Dan jumped into his presentation. He explained the details of his implementation and how it worked, begged for contributors, and in five minutes it was over. The crowd applauded politely, and he left the stage.

If we look at how Appium came into existence, lightning talks are a very important part of this journey. Continuing the tradition at Selenium Conf, we would like to dedicate a full session with all attendees on Lightning talk.

Submit your topic for a 3-min lightning talk. If you have slides or videos from past presentations, please include them to maximise your chance of getting selected. Selected speakers will get a free pass to the conference.

Q & A with the Selenium Committer's Panel moderated by Pooja Shah

Follow along with one “Lazy Testers” journey where we redefine “lazy”, look at why doing less work isn’t always a bad thing, and where being “lazy” can benefit teams and workplaces.

Fireside Chat between Manoj Kumar (Selenium Committer and a member of the Project Leadership committee - Selenium) and Puja Jagani (Selenium Project Committer and member of Technical Leadership Committee)

In the talk I'm going to give an update on the WebDriver BiDi protocol development. What is the specification status, what are Web Platform Tests and what is done there so far, and what is the implementation status on different browsers.

Looking back at test automation in a product development team for describing patterns of success for research purposes, we identified themes where the experienced success significantly differed from what the literature at large was describing. With those lessons, I moved to a new organization and took upon myself to facilitate a transformation to whole-team test automation over multiple teams, one at a time, one after the other. In this talk, we will revisit the research from one organization two years ago with lessons from another in the last two years. 

In this talk, I will introduce you to my core patterns to practice-based test automation transformation. I can't promise a recipe I would apply, as my recipe changes and adapts as I work through teams, but I can promise experiences of the same patterns working on multiple occasions as well as examples of how my go-to patterns turned out inapplicable. We'll discuss moving from specialist language to generalist language, visualizing testing debt and coverage, using visualization to showcase progress made of continuous flow of small changes, choosing to release based on automation no matter how little test automation there is, and growing individual competencies by sharing YOUR screen when working together. 

At this workshop, you'll learn about advanced concepts in Appium. We will learn how to write a single script for Android, iOS, and mobile web apps. Once our tests are established, we will work on the framework design and report. We will also have a detailed look at how can we automate various mobile gestures using Actions API and mobile endpoints in Appium. The workshop will be based on the latest Appium's Java Client.

Prior to Selenium, engineering teams around the globe were struggling to build and maintain their own web testing solutions. Most frameworks at that time neither supported testing the front-end behavior of web applications, nor executing tests across different browsers and operating systems.  This forced teams to fill that gap with homegrown solutions and they were doing so in silos, without the support and backing of the open-source community or browser development companies. As we know, Selenium changed all of that and WebDriver has been a saving grace for development teams. However, the rise of Selenium unveiled a hidden set of web UI test automation challenges, many of which are still prevalent today.

Join Tariq King as he takes you on a journey to address those challenges through an evolutionary tale of test automation framework development. Based on a true story, the tale starts with replacing a rigid homegrown solution with a more flexible internal Selenium-Based Domain Specific Language (DSL), and then extending that into an external DSL with powerful test management and software process integrations. The next step in the evolution incorporates AI-based element selection and self-healing features into Selenium. Curious about where the story goes or how it ends? Tariq will share his thoughts on the future of web UI test automation with Selenium.

There's been a lot of discussion around Python. According to several surveys, it is one of the most in demand languages today. It's also particularly good for test automation. Whether you are a manual tester who is just learning to program for the first time, or you're a seasoned developer, Python is a great language to use.

Join Applitools Developer Advocate, Andrew Knight as he demonstrates how you can build a UI testing solution from the ground up using pytest and Selenium WebDriver. At the end, you'll understand how to create your own fully working solution to extend with any tests that you want.

In this 20 minute session, I will demonstrate the use of Appium and AltUnity Tester, an open source automation tool for Unity, to write automated tests for a game. I will briefly show why this is a challenge with just Appium and how adding AltUnity Tester to the mix allows us to identify game objects and interact with them just like we would in a native mobile app.

With digital transformation, businesses are aspiring to release features as soon as it's developed, which brings considerable challenges for the Testing team. While there are many, the most critical ones revolve around an improper test infrastructure and execution time of test cases at scale.

In this talk, I will cover the below problem statements and share my experience with the audience on how businesses are solving these problems:

1. Lack of Test Environment
2. Automation Testing at scale

Have you ever wondered how you can contribute to the Selenium project and become part of the team?

Do you wonder how the different Selenium projects work under the covers?

Selenium is a set of solutions that enables you to automate all major browsers with WebDriver, scale up and run tests in parallel through the Grid, record and play back user interactions with the IDE, and share all this knowledge though the Selenium website and documentation.

However, only a handful of volunteers work to maintain this gigantic effort. If you would like to enhance your own Selenium experience while contributing back to the software that has defined so many of our careers, come to this workshop. In it we'll dissect the different elements of Selenium, dive into its internals, learn how it was built and how to make changes to it, and even fix or improve something that you can contribute on the same day!

The goal of testing is to release high-quality software. To do this, developers need to find and fix defects quickly. Debugging hence becomes a critical part of any testing workflow.
In this talk, we discuss how Nightwatch, coupled with Selenium 4, can help developers quickly identify why a test has failed, and extract the necessary information to solve the issue.

Selenium Grid can be a bit daunting to get up and running. Starting it is quite easy, but using it effectively can require pulling in third-party tools. In this workshop we’ll cover how to run your grid effectively, using best practices culled from several large grid installations.

Web applications evolved a lot in the last few years to a point where traditional testing approaches and tools are not good enough. Along with that evolution, new web frameworks changed how web applications are written and tested. Testing strategies are now more important than ever, together with a division of testing responsibilities across the team, and a deeper understanding of the web application under test.

Evolution, community feedback and standards have also made Selenium evolve during the last few years. How does Selenium fit now in your testing puzzle? New features like network interception, event listening, and mutation observation can help you make your tests more complete and resilient. We will go through some of these features in Selenium, and how they can help you create fast feedback loops to improve the experience of writing and testing software.