Selenium News and Updates: A Smattering of Selenium 102
A careful look back at Adam Goucher’s July 2012 Selenium roundup: what it covered, what its links can tell us, and what needs rechecking today.
“A Smattering of Selenium #102” is a link roundup by Adam Goucher, published on the official Selenium project blog on July 17, 2012. It records what the browser automation community was discussing at that moment; it is not a current Selenium release note or a present-day setup guide. Treat its tool references and opinions as historical context, and check current project documentation before using them to make implementation decisions.
This article summarizes the roundup’s scope, explains its Selenium comparison in context, and offers a practical way to use an old technical roundup responsibly. For current website screenshots without configuring a browser, ScreenshotNeo is an option to consider; details and a direct request appear below.
What “A Smattering of Selenium #102” is
Goucher’s post is a short collection of links and observations, not a systematic survey. Its opening notes that his body was not yet on “left coast time,” then moves through a range of engineering topics around browser automation and testing.
The subjects include making a large HTML table behave, Rails caching and HAR files, Dropbox scaling, finding broken links, implicit and explicit waits, pytest parametrization, CI build-agent sizing, a JavaScript combo box controlled with WebDriver, an RSpec release, and speeding up Android tests with Calabash. That breadth makes it useful as a snapshot of the conversations surrounding Selenium in mid-2012, rather than as a focused guide to any one technique.
What the roundup says about Selenium tools
One link demonstrates finding broken links in a webpage with Selenium RC. Goucher observes that the example does not use Selenium itself to follow each link. He calls the idea sound and writes that this is why, in his view, Selenium RC and WebDriver were “soo much more powerful than Se-IDE.”
That is Goucher’s opinion in a specific 2012 example. It should not be presented as a current comparison, benchmark, or general ranking of Selenium tools. The point he was making was about the interaction model in that example: browser automation can be combined with other code that checks links, rather than relying on a recorded browser interaction alone. The roundup does not establish the present status, capabilities, or recommended use of those tools.
How to use a 2012 roundup responsibly
- Keep the date attached. The source was published July 17, 2012. Browser drivers, APIs, dependencies, and testing practices can change substantially over that timespan.
- Separate a link from evidence. A link proves that the roundup pointed readers to a resource; it does not prove that the resource remains available or technically current.
- Find current primary documentation. Before adopting a wait strategy, framework integration, driver workflow, or CI configuration, consult documentation for the versions you actually use.
- Preserve attribution. If discussing the RC/WebDriver/IDE comparison, attribute it to Adam Goucher and explain that it was his assessment of the linked broken-link example.
- Do not turn the roundup into release guidance. It is a community link collection, not a Selenium changelog or compatibility matrix.
What it can and cannot tell you
| The roundup can tell you | It cannot establish by itself |
|---|---|
| Which topics and links Goucher selected in July 2012. | Whether each external page is still online or accurate. |
| How he interpreted the linked Selenium RC broken-link example. | How Selenium products compare today, or which one you should choose now. |
| That Selenium discussions touched adjacent areas such as caching, CI, test frameworks, and Android testing. | Current browser compatibility, supported versions, APIs, or best practices. |
Capture a page for a test or review
A screenshot can help preserve the visible state of a page when documenting a visual issue or reviewing a test result. The roundup itself does not provide a modern screenshot workflow or validate any screenshot tool. For a current capture, use the browser automation setup and documentation appropriate to your project, or make a direct screenshot API request as shown below.
Or skip the browser setup
ScreenshotNeo’s API documentation describes its screenshot API. A GET request can return an image or PDF. This runnable cURL example saves a WebP capture of Stripe:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpPython:
import requests
r = requests.get(
"https://api.screenshotneo.com/v1/shot",
params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
timeout=90,
)
r.raise_for_status()
open("shot.webp", "wb").write(r.content)Node.js:
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await require('node:fs/promises').writeFile('shot.webp', Buffer.from(await res.arrayBuffer()));ScreenshotNeo removes cookie and consent banners, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing status. Its MCP server lets AI agents use screenshot, page-info, and PDF-capture tools. The free plan includes 1,000 screenshots per month without a card; paid plans start at $5 for 3,000. See the docs for request options, then sign up for 1,000 free screenshots a month with no card.
Common questions
Is this a Selenium release announcement?
No. It is a link roundup with brief observations, published in 2012.
Does the roundup prove Selenium RC or WebDriver is better than Selenium IDE today?
No. The comparison is Goucher’s historical opinion about one example. Use current project documentation to assess present-day tools.
Are the roundup’s linked resources still valid?
The research reviewed the official Selenium post, not every external link. Check availability and current documentation before relying on those resources.
Source note
Historical details and the attributed tool comparison in this article come from the official Selenium project post, “A Smattering of Selenium #102”. The linked third-party pages were not independently checked for current availability or accuracy.
