You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Thanks for contributing to the Selenium site and documentation! A PR well described will help maintainers to review and merge it quickly
Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, and help reviewers by making them as simple and short as possible.
Description
add episode 6 blog
Motivation and Context
add episode 6 blog
Types of changes
Change to the site (I have double-checked the Netlify deployment, and my changes look good)
Code example added (and I also added the example to all translated languages)
Improved translation
Added new translation (and I also added a notice to each document missing translation)
The blog post doesn't include details about the actual content or topics discussed in Episode 6. Consider adding a summary of the key points, topics, or takeaways from the presentation to make the post more informative.
**Selenium Community Live - Episode 6**
Luke Hill is a Lead QA Engineer at Dexters with extensive automation expertise across FinTech, E-Commerce, and Education sectors. A passionate open-source contributor, Luke owns site_prism (a Page Object Gem extending Capybara), serves on the Cucumber technical committee, and is a maintainer of Selenium. Known for his meticulous testing approach and ability to identify challenging edge cases, Luke consistently helps teams deliver more reliable code. His technical expertise in both frontend and backend testing makes him a valuable voice in the QA community.
The LinkedIn URL contains an incorrect episode number (episode67325906639075581953). This appears to be a formatting error where the episode number and a unique identifier were combined. Update the URL to reference the correct episode number.
You can watch the episode on YouTube here- **<a href="https://www.youtube.com/live/48g7sOBHEL0?feature=shared" target="_blank">Episode 6 on YouTube</a>**
or
-You can watch the episode on LinkedIn here- **<a href="https://www.linkedin.com/events/seleniumcommunitylive-episode67325906639075581953/theater/" target="_blank">Episode 6 on LinkedIn</a>**+You can watch the episode on LinkedIn here- **<a href="https://www.linkedin.com/events/seleniumcommunitylive-episode6/" target="_blank">Episode 6 on LinkedIn</a>**
Apply / Chat
Suggestion importance[1-10]: 4
__
Why: The suggestion assumes the LinkedIn URL contains a formatting error, but LinkedIn event URLs typically include long numerical identifiers. Without verification that this specific URL is incorrect, the suggested change might break a valid link.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
User description
Thanks for contributing to the Selenium site and documentation!
A PR well described will help maintainers to review and merge it quickly
Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, and help reviewers by making them as simple and short as possible.
Description
add episode 6 blog
Motivation and Context
add episode 6 blog
Types of changes
Checklist
PR Type
Documentation
Description
Added new blog post for Selenium Community Live Episode 6
Included event details, speaker bio, and recording links
Provided references to speaker's profiles and related resources
Changes walkthrough 📝
selenium-community-live-episode6.md
Add new blog post for Selenium Community Live Episode 6website_and_docs/content/blog/2025/selenium-community-live-episode6.md