Add blog post on using AI coding agents with Selenium - #2853
Merged
Merged
Conversation
Announces the new AI agents documentation page added in #2846. The post takes the angle that agents are not hallucinating when they emit Selenium 3 code - they were taught by a decade of blog posts and tutorials, a good share of which this community wrote, and which still outnumber everything published since. From there it pulls out the three things worth acting on: point the agent at llms.txt, write the project rules into AGENTS.md/CLAUDE.md, and let it drive a real browser so locators are verified rather than inferred. Singles out one pattern for review: agents "fixing" a flaky test by raising a timeout or adding a sleep, which hides the race instead of removing it. Links to the documentation page rather than restating it, so the post stays short and the docs remain the reference. Co-Authored-By: Copse <noreply@copse.dev> Copse-Models: acp:claude-agent-acp#opus[1m]
✅ Deploy Preview for selenium-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
diemol
approved these changes
Sep 29, 2026
selenium-ci
added a commit
that referenced
this pull request
Sep 29, 2026
Announces the new AI agents documentation page added in #2846. The post takes the angle that agents are not hallucinating when they emit Selenium 3 code - they were taught by a decade of blog posts and tutorials, a good share of which this community wrote, and which still outnumber everything published since. From there it pulls out the three things worth acting on: point the agent at llms.txt, write the project rules into AGENTS.md/CLAUDE.md, and let it drive a real browser so locators are verified rather than inferred. Singles out one pattern for review: agents "fixing" a flaky test by raising a timeout or adding a sleep, which hides the race instead of removing it. Links to the documentation page rather than restating it, so the post stays short and the docs remain the reference. Copse-Models: acp:claude-agent-acp#opus[1m] Co-authored-by: Copse <noreply@copse.dev> [deploy site] 94c7cbd
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Announces the AI agents documentation page added in #2846.
The post takes the angle that agents are not hallucinating when they emit Selenium 3 code — they were taught by a decade of blog posts and tutorials, a good share of which this community wrote, and which still outnumber everything published since. From there it pulls out the three things worth acting on:
llms.txtAGENTS.md/CLAUDE.mdIt singles out one pattern for review: agents "fixing" a flaky test by raising a timeout or adding a sleep, which hides the race instead of removing it.
The post links to the documentation page rather than restating it, so it stays short and the docs remain the reference.
Notes for review
chrome_fornightly_releases.md. I was not able to run a local Hugo build to confirm rendering, so worth a look on the deploy preview.[deploy site]in the commit, so this will not deploy on merge.🤖 Generated with Claude Code