iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
“A Smattering of Selenium #67” was a Selenium community link roundup published on October 27, 2011—not a current release announcement. Written by Adam Goucher, it collected links about behavior-driven development, large continuous-integration systems, AJAX and SVG testing, Selenium RC speed, and queries after load tests.
What was “A Smattering of Selenium #67”?
It was one entry in Selenium’s historical “Smattering” series. The official archive lists it among the project’s 2011 posts as a General-category item tagged “Smattering.” Selenium’s official blog archive lists the post and its publication date; the original post is available at “A Smattering of Selenium #67”.
The date matters: the post is a snapshot of topics circulating in the Selenium community in 2011. Its links and comments should not be read as current recommendations, release notes, or confirmation that a tool remains maintained or compatible.
Which topics did the roundup link to?
Spinach and behavior-driven development
Goucher opened with Spinach, describing it as a Cucumber-esque behavior-driven development (BDD) framework advertised as having “less regex magic.” He wondered whether it had gained Selenium support and expected it might. That was his expectation in 2011, not evidence of confirmed compatibility then or now.
#1 Best Overall
Large continuous-integration systems
One link concerned coping with large continuous-integration (CI) systems. The roundup points readers toward the article; it does not present a general CI design, a comparative evaluation, or a current recommendation.
AJAX testing and page loading
Another link discussed “reintroduced page loading” in the context of testing AJAX applications with Selenium. This is a historical testing topic, not a statement about how current Selenium versions handle page loads.
Rank #2
SVG games and an Angry Birds robot
The collection also included an article about testing an SVG game and a report on Jason Huggins’ Selenium robot playing Angry Birds. These entries show the roundup’s range, from browser-based graphics to a demonstration involving physical automation.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallSelenium RC execution speed
A linked article addressed faster Selenium test execution specifically in Selenium RC. The post’s aside asking whether XPath engines differed in speed is a question, not a benchmark or a verified performance comparison. Neither point should be generalized to modern Selenium drivers.
BrowserMob queries after load tests
The final topic was BrowserMob ad hoc queries to use after Selenium-based load runs. The roundup identifies the subject, but does not provide current service details or recommend BrowserMob for present-day load testing.
What the post does—and does not—establish
- It documents which Selenium-related links Goucher chose to share on October 27, 2011.
- It does not establish present-day Spinach compatibility, project maintenance, or the status of any linked tool or service.
- It contains no formal product comparison, named statistic, or documented performance test.
- Its question about XPath speed is not evidence that one XPath engine was faster than another.
Selenium’s current site lists BrowserStack, Sauce Labs, and LambdaTest as Development Partners. That present-day listing provides ecosystem context only; it does not show that those companies appeared in the 2011 roundup or establish any affiliate or commission arrangement. See the official Selenium site for current project information.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.ScreenshotNeo for capturing pages in a current workflow
The 2011 roundup was a set of links, not a screenshot-tool comparison or how-to. For a present-day workflow that needs website screenshots, ScreenshotNeo is a separate option: its API returns PNG, JPEG, WebP, or PDF captures, and it can remove known consent banners, newsletter popups, and chat widgets before capture. Only clean shots are billed; bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, with the response indicating the page verdict and billing status. Its MCP server offers screenshot tools for AI agents.
For browser automation or test capture, choose the method that fits your need: Selenium gives you browser-driven test control, while ScreenshotNeo provides a screenshot API and MCP tools. The 2011 post does not compare these approaches.
ScreenshotNeo has 1,000 shots per month free with no card; paid plans start at $5 for 3,000 shots. All features are available on every plan. See the ScreenshotNeo documentation and try the free sign-up.
Quick Recap
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.
