Pallavi Sharma will present a workshop on using Selenium for automated web testing, regardless of programming language. 
Discover Selenium’s features, the basics of web automation, and how to get started effectively.
Not registered yet? Don’t miss out—secure your free tickets now.
Already registered? Share your questions in the thread below 
Hi there,
If you couldn’t catch the session live, don’t worry! You can watch the recording here:
Here are some unanswered questions that were asked in the session:
Can we integrate AI tools with Selenium scripts?
Can we expect any demo on the implementation to integrate AI testing?
What role does Selenium play in CI/CD pipelines, and how can it be optimized for continuous testing?
Something about how can we integrate Selenium AI?
How does Selenium plan to evolve our QA industry in a positive way? If we as testers are the drive force of quality, what depth of knowledge do we need to gain in order to drive the product correctly and manage the risk of delivery?
How can we extend Selenium to integrate AI-driven testing or improve test maintainability?
What are the best tools for training to learn or upskilling with Selenium?
What role does logging play in Selenium tests, and how can you ensure that logs provide meaningful insights for troubleshooting?
Can we get a demo of how to integrate Selenium tests into a continuous integration/continuous deployment (CI/CD) pipeline?
Please do a demo on how to integrate Selenium in AI-driven testing.
Beyond the basics, what are the advanced strategies for ensuring comprehensive cross-browser testing with Selenium?
What new features and improvements can we expect in the upcoming versions of Selenium?
What strategies can be employed to reduce test maintenance overhead in large Selenium test suites?
Can you provide a brief for setting up Selenium in a Linux/Unix environment? Links for any articles would be helpful.
How to implement Selenium AI?
Here are some answered questions that were asked in the session:
What do you think are the strong points of Selenium compared to competitors like Cypress and Playwright? What about weak points?
Pallavi Sharma: Strong and Weak Points of Selenium:
Strong Points: Selenium offers extensive browser support, a large community, and mature integrations with various testing frameworks and tools. It supports complex test scenarios and is highly customizable.
Weak Points: Selenium can be slower compared to Cypress and Playwright due to its architecture and the fact that it interacts with the browser through WebDriver. It may also require more setup and configuration compared to the more streamlined setups of Cypress and Playwright.
If some one want to contribute to selenium, where one should start?? what are the pre-requisites for this project ??
Pallavi Sharma: Start by exploring the Selenium GitHub repository to understand its structure and current issues. Look for open issues labeled as “good first issue” or “help wanted” for beginner-friendly tasks. Pre-requisites include familiarity with Selenium’s architecture, basic programming skills in languages used by Selenium (like Java, Python, or JavaScript), and understanding of testing concepts.
What are the key considerations for ensuring that Selenium tests comply with data privacy regulations, such as GDPR, when dealing with sensitive data?
Pallavi Sharma: To integrate Selenium tests into CI/CD pipelines, use tools like Jenkins, GitHub Actions, or GitLab CI/CD to automate test execution. Set up your pipeline to trigger Selenium tests upon code commits or deployments, and configure the pipeline to collect and report test results. Ensure your test environment is consistent with your staging or production environments for reliable results.
