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

Q & A with the Selenium Committer's Panel moderated by Anand Bagmar

Jim has been one of the longest contributor to the Selenium Project. In this fire-chat chat, he will share his reflections on the past, the present and the future of Selenium and test automation in general.

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.

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

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)

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.

Ensemble testing - a whole group working at the same time on the same computer - is about learning practical skills in the context of applying the skills to a real problem. In this session, our real problem is testing location based content on websites. Selenium 4 gives us a chance of setting up the basic use case for this: pick up a test target, drive it with code collecting geolocation-based screenshots on multiple browsers on a grid to explore the location based differences. 

We set up an ensemble testing session facilitated in popcorn style. We take volunteers from the audience to be our hands and brains on a shared computer, rotating frequently on who is on the keyboard and in control of decisions, to work together to automate a scenario. While you can pick up new information even if you know the technologies in use, you don’t need to know the feature under test or the features of selenium 4 to participate in this session, it is enough we have some people that do. We expect participants to be ready to take part in testing in a facilitated environment where we work together as a group in learning the application and testing. We will test on an instructor machine with a Java 11 Selenium 4 with webdriverManager and Selenium Server on IntelliJ idea, and the lessons you draw are applicable across languages, and knowledge of Java is not required to learn in this session. 

In ensemble testing, we care about both learning and contributing.  Software development is not about getting the most out of us, but the best out of us - avoiding the ping pong, creating ideas we would not generate alone and sharpening our skills. We don't know what we don't know but can recognize it in the context of doing it. Those who learn the fastest, do best.

One billion people are estimated by the World Health Organisation to have a disability. W3C's Web Content Accessibility(A11y) Guidelines (WCAG) are becoming increasingly mandated by governments. They are being used by many industries to make websites more accessible for people with disabilities. The product development team is often told to make their websites accessible like it is an easy light switch you turn on or off, but, it is not easy.

Digital transformation is now the holy grail of IT organisations. However, most companies are striving towards engineering excellence with processes like the Continuous Delivery process and often forget about the usability and Accessibility factor, which has to be given utmost importance early in the cycle. Because the applications/ products that we build should be accessible by all.

"Accessibility is everyone's responsibility" - We all need to understand that Accessibility isn’t “someone else’s job”. In this talk, Manoj intends to share some practical examples of baking Accessibility during your agile software development cycle and advocates striving for engineering excellence with empathy. This talk will include basics like, need for Accessibility, followed by some practical, simple ways to find Accessibility flaws and, this will enrich the level of confidence to have some meaningful conversation about pushing for Accessibility mindset at their workplace and how to take it forward by baking in the accessibility at part of your Agile process from planning stages to production stages.

This talk will share practical insights on how to bring in the Accessibility mindset within teams and highlight tools and processes in the Accessibility ecosystem to implement during product development, 

• Where to start with Accessibility?
• Can we add Accessibility into the Definition of Done?
• What audit tools to use in the software dev lifecycle
• How organizational transformation on Accessibility initiative can be done to promote the Accessibility thought process.

Digital Transformation is now the holy grail of IT organizations. However, most companies are still struggling with setting up a proper Continuous Delivery process, which shall help the transition into shorter release cycles and faster, more frequent deployments to production.

Teams may already be familiar with Continuous Integration, Continuous Delivery and Continuous Deployment (the 3Cs) and the differences between them. However, to make these 3Cs possible, we need a fourth C, namely Continuous Testing (a.k.a Test Automation.) Continuous Testing is the fast feedback mechanism that assists the 3Cs and is one of the most difficult challenges for digital transition.

In this talk, I'm aiming to cover the top continuous testing pitfalls and how companies are solving these problems. This talk is based on practical examples that include key pitfalls around:

• Test Data management
• Choosing the right tool/framework
• Deciding on what to automate?
• Is In-Sprint Automation possible?
• Is automation part of Definition of Done?
• Effective collaboration
• Test Environments
• Flaky tests

It's time the testers took control! And use some of the modern tools that help address those problems. This talk will cover tech stack like Selenium, Appium, PlayWright, Taiko, Docker, Kubernetes, Grafana/Kibana, TestContainers.

Q & A with the Selenium Committee moderated by Anand Bagmar

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.

A few months ago Appium migrated to W3C protocol, added AI, and integration for custom plugins for element search, that anybody can implement. Apple released Xcode 10 with abilities run XCUITest in Parallel. Google released EarlGrey with support for accessibility in iOS12 and then there is Flutter with its driver package for integration testing.

As you see, there has been a lot of recent developments and additions in the mobile testing world. This talk aims at covering them and also review its current state and suggest some key pointers when selecting a tool and review their usage and weaknesses

Selenium: State of the Union

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.