A Smattering of Selenium #69 is a short archival link roundup by Adam Goucher, published on November 22, 2011—not a Selenium release announcement or a current-news bulletin. Its links focused on practical test automation, including WebDriver synchronization, dynamic forms, Page Objects, and continuous integration.
What was A Smattering of Selenium #69?
It was one issue of the Selenium project’s “Smattering” blog roundup: a collection of links and brief descriptions rather than a report on a new Selenium version. The official Selenium blog lists Adam Goucher as the author and classifies the post under General, with the tag Smattering. The page records a later modification on August 7, 2021, described as a directory rename; that note does not change the original publication date.
As an Amazon Associate I earn from qualifying purchases.
The post is best read as a snapshot of Selenium-related reading shared in 2011. Its descriptions reflect the author’s account at that time; they do not establish that the linked projects remain available, maintained, or recommended today.
What topics did the roundup cover?
- Continuous integration: ideas collected from the most recent CITCon iteration as of the post’s 2011 publication.
- Authentication testing: a Rails 3 technique using Cucumber, Capybara, and Selenium.
- Packaging: Pennyworth, described in the roundup as a continuous packaging system.
- Acceptance testing and design: JBehave, Selenium, and Page Objects.
- WebDriver timing: guidance about synchronization and deciding when to wait.
- Dynamic forms: using WebDriver with JBehave to test web forms that change dynamically.
- Data-driven testing: a JUnit test kata involving DDT.
- Automation balance: an article proposing “smell tests” for overreliance on one type of test automation.
- Python decorators: a library roundup that the post said listed 31 implementations at the time. That is a count reported in 2011, not a current or independently verified total.
What did it say about Bromine?
The roundup reported that Bromine was ending development and described it as powered by Selenium. This is a statement about the project’s status as presented in November 2011; the post does not verify Bromine’s status now.
#1 Best Overall
How to use this issue today
For historical context, the issue gives a useful map of concerns Selenium practitioners were discussing in 2011: integrating tests into continuous integration, making tests work with dynamic interfaces, and choosing synchronization points. Treat the linked material as period reading, not as current setup guidance. The roundup alone cannot confirm whether a linked page is still online or whether a described technique fits a modern application.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.A current option for capturing pages during development
If your work involves capturing website screenshots alongside browser testing, ScreenshotNeo is a separate screenshot API and MCP server for developers. It is not a tool identified or endorsed by the 2011 roundup. Its API accepts a URL and returns an image or PDF; see the ScreenshotNeo documentation for request options.
Rank #2
For example, this cURL request saves a WebP capture of Stripe; replace the URL and provide your API key:
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
Best Value
Rank #4
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp
ScreenshotNeo says it removes supported cookie-consent banners, newsletter popups, and chat widgets before capture, and that bot checks, blank pages, timeouts, failed loads, and cache hits are not billed. It also offers an MCP server with screenshot and PDF tools for AI agents. The Free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for the free plan.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

