Has quality been put in a box? Has its focus and scope been narrowed to a single step in the delivery process? Has the role of quality in your organization been relegated to the test step, and its value beyond that diminished? Join Erika Chestnut as she shares how she breaks out of the box and crosses the aisles to elevate and expand the role quality in her organizations.  Learn how to influence from the middle, socialize the full potential of quality and cultivate a culture of quality defined, developed, and driven by Quality Champions.

If you took the time to sit down to answer the question “what do you do as an Automator on a daily, weekly or monthly basis”, what would you come up with? Would it just be coding, coding and more coding or would your answers highlight a wide and wonderful range of activities you carry out?

For a skilled Automator, success relies on more than just being comfortable with programming languages and tools. It requires a diverse range of skills, techniques and experiences which the newly released Ministry of Testing automation curriculum has captured and organised in a way so that everyone can see the abilities an Automator has or can attain.

In this talk, Mark will share how his own experiences and the experiences of other automators have helped curate the Ministry of Testing automation curriculum. Through these stories, we’ll learn how the journey of an Automator is a varied one that can easily employ pen, paper and questions as much as IDEs, frameworks and libraries. We’ll also learn how an open source community curated curriculum can help you regardless of your abilities, role and context and how you can help it grow by sharing your own experience.

To be able to create automation test cases using a frontend UI automation framework like Selenium or Appium is easy enough. The hundreds of test cases in your suite should give you a clear answer towards the health of your build. But what is the reality? The test suite has many failures that need hours of analysis to identify actual bugs vs. test case instabilities and false positives. Developers do not trust the automation and the QE feels testing manually would have been easier and faster.

What is the solution? Rewrite your entire suite and reskill your entire team? The answer to converting your entire test suite to stable full stack automation test cases is simpler than you imagine. Our solution utilizes an open-source proxy solution to be able to record frontend and backend interaction while executing a frontend test case. The CI infrastructure then replays these recordings to be able to test frontend workflows without any dependency on backend services, which are prone to changes, time outs and outages. Results show stability of frontend test cases greatly improved without the added complexity of real time backend interaction. Our talk walks through what kind of test cases are best suited for this conversion, what considerations to make while choosing the proxy solution, how this should be configured, how CI should support this change and how to compliment the proxy tests to make sure backend services are healthy and working as expected. 

When I started the Selenium project, I'd frequently describe Selenium as "like a robot" that is trapped inside your computer. For the past 11+ years, I've been testing that metaphor by building real mechanical robots for testing apps and devices, pushing the definition of "end" in end-to-end testing. Lately, I've been remotely controlling these robot over the internet, and learned some lessons I'd like to share. In this talk, I'll compare and contrast how testing with a physical robot over the internet is different than traditional testing approaches with Selenium or Appium.

At this full-day (480 mins) 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 JavaClient.

In this talk, Noemi will cover key concepts about crawlers - what they are, why and when we need them, types of crawlers, and their components. We will see a demo for creating and using crawlers with Selenium, and the pros and cons of doing so.

Four years working as a tester in a consulting company, I had learned enough to do well on my job. I knew something called automation but had yet to work on it. Looking around for learning led to realizing there were few people to learn from as unemployment in Africa was blocking access to people with experience. I started teaching and learning through teaching.

Now 1000+ students later, I teach a basic course on testing introducing automation with java+selenium and an intermediate course with js/java/python with Selenium, Appium, and rest APIs. The market wants automation testers. Automation has become paramount. 

This talk discusses my dream of removing unemployment in Africa through software testing. Realizing the dream starts with one person, teaching many. Many then speak of their life-changing experiences of joining tech. It’s a story of a hobby on the side of testing work, growing into a training business, and learning automation and Selenium with the students I have taught. 

Selenium has been a game changer for people. During the Testify programs, Selenium has played a massive role in benching the wheel of test automation, which has helped several novices navigate the waters of automation easily. Join me in ensuring that by 2030, every graduate in Africa no longer has to worry about unemployment through testing and also how Selenium sits at the heart of this very solution.

Selenium WebDriver v4 was released in Oct 2021. This version of Selenium WebDriver brings new features and capabilities for automation. At the same time, there are some features that are now deprecated and changed.

If you answer yes to any of the following questions, this workshop is for you!

• Are you using Selenium 3 and want to know how or why to update to Selenium 4?
• Have you written Selenium tests before, but want to know about the advanced features?
• Are you are struggling with flaky tests and want to learn strategies for fixing them?

This practical, hands-on, course is designed to help automation engineers take their Selenium expertise to the next level. All attendees will leave with working Selenium WebDriver code on their machines and many techniques to successfully use the Selenium WebDriver API in their own context.

A little history .... 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 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 SeleniumConf Chicago 2023, we will be offering a Lightning Talk track session. Each presenter will be given a maximum of 5 minutes for their talk. Here's how it works: on the first day of the conference there will be a sign-up board for any attendee to write down their topic and contact information. All attendees will be encouraged throughout the day to stop by the board and add a tick mark to upvote the talk(s) they'd like to hear. Once voting has ended, the organizers will track down the top 6-7 vote getters and provide additional details to help them prepare for their talk.

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! For the first time ever, we are offering this workshop at no charge to a limited number of qualified applicants - you only need to purchase a regular conference ticket to gain an extra workshop day! Learn more and submit your application here.

Please note this is not a Selenium training workshop, but instead a walk-through of the project's codebase with guidelines on how to contribute.

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.

Page Objects design pattern is commonly used by most automation developers because it provides encapsulation and ensures maintainability of UI tests. The larger and more complex is application, the more UI tests teams have to write and maintain, and the more important it is to maintain 1:1 relations between UI component and a Page Object. But design pattern on its own does not ensure good quality of the page object code, that's why we created UTAM.

UTAM provides declarative JSON based language to create page objects and compilers to transform declarative code to Java, JavaScript or TypeScript. Generated code is based on Selenium library (for Java) or WebdriverIO (for Javascript), but UTAM allows to build custom integration layer to use any framework for UI interactions. Generated code is high quality and uses all best practices like explicit waits and CSS selectors only (XPATH not supported). It's very easy to write UTAM JSON and even easier to generate it automatically from any HTML source.

UTAM declarative language has support for mobile automation as well (both IOS and Android) and Shadow DOM.

We provide extensive documentation and online interactive tutorials on UTAM web portal https://utam.dev/tutorial/introduction for better learning experience. We also created browser extension to partially generate UI tests https://chrome.google.com/webstore/detail/utam/llgodnekeleaidcljgfljjechnjdgnli 

Our goal with UTAM is to increase maintainability of the page objects and development productivity to produce overall better experience.

Good data for testing can be a nightmare to manage. Sometimes, teams don’t have much control over the data in their systems under test—it’s just dropped in, and it can change arbitrarily. Other times, teams need to build their own data sets, either before testing or during testing. Inaccurate data can leave test gaps. Incorrect or stale data can break tests. Large data can consume too much time. Ugh!

In this talk, we’ll cover strategies for defeating many types of test data nightmares:

• recognizing the difference between product data and test case data
• deciding when to prepare data statically beforehand or dynamically during testing
• using data to control how tests run or reflect product state
• hard-coding values versus discovering data in the system
• avoiding collisions on shared data

The strategies we cover can be applied to any project in any language. After this talk, you will wake up from the nightmare and handle test data cleanly and efficiently like a pro!

With more frontend frameworks on the rise web component testing becomes a crucial part of everyones testing stack. It allows to test various features of a single component of your UI and can help to reduce the amount of e2e around it that usually would run slower.

There are already many component testing tools available but almost all of them miss an important feature: running the test in an actual browser. While one might argue that running test in a virtual DOM is fine for testing why not just run them in the browser if you can. With WebdriverIO v8 and its new browser runner capabilities, you can now execute unit or component tests directly in the browser with no complicated set-up required and use the power of the WebDriver protocol to seamlessly interact with them, as a user would do.

In this session, Christian Bromann, Founding Engineer at Stateful, will tell you all about the new browser runner capabilities and will show case hands on live demos testing components in Vue, Svelte, React or Preact. Be amazed as component testing has never been so easy before!

Today’s modern development disciplines -- whether Agile, Continuous Integration (CI) or Continuous Delivery (CD) -- have completely transformed how teams develop and deliver applications faster. But in order to compete in today’s fast-paced digital economy, companies must also test faster and test continuously. Teams must make fast and reliable decisions by tracking test results of thousands tests for hundreds of runs triggered by code changes. 

But what if we could leverage Machine Learning to do the analysis and help team make rule-based decisions using a concept named Quality Gates?

In this presentation, I will share learnings derived from regressions in 200,000 test cases, and how we use Machine Learning (ML) to triage failed reports and reduce team effort on results analysis. How we organized a Quality Gates and formed a rule-based engine to identify Go and No-Go decisions for a particular set. And how we automate release pipelines by use of meaningful feedback from the automated testing results.

You will learn how to build Quality Gates in ReportPortal, how to integrate feedback within CI/CD pipelines. How to utilize ML analysis in triaging of failed reports. And finally make a leap forward to Continuous Testing.

All of us have tested on either headless browsers, browser engines or responsive mode for mobile. However, there are a lot of differences between an actual browser, desktop and mobile, vs a simulated one.

In this talk I’ll walk you through real world examples that show you the gaps you can miss while testing:

1. In headless mode

2. Browser engines

3. Responsive mode for mobile browsers

I’ll also share the technicalities of why this happens and my learnings from having worked on a browser engine.

You have implemented your site functional tests with Selenium. Now, how can you reuse some of these tests to verify that your site does not only work as expected with 1 user, but with a big load of them? In this talk I will show you a way to achieve this without leaving your IDE.

I will do a live demo generating a load script using JMeter DSL, from an existing Selenium script. Then, I will run it in combination with the Selenium script to generate load and evaluate user experience while such load is being imposed.

Join me, add JMeter DSL to your toolbox and let's share some fun & ideas!

If you answered “yes” to the question, then welcome to a world where we will discuss the non-testing use cases for our dear driver (pun intended).  

In this session, we will break the mould, and discuss the various use cases for our browser automation tool. We will start with testing but go on to demonstrate how you can build a poor man’s version of RPA (Robotic Process Automation) tool with a little code.