A Smattering of Selenium #84 is a Selenium community link roundup by Adam Goucher, published June 11, 2012. “84” is the post’s place in the series—not a Selenium release number. Its links range from page objects and Robot Framework test batching to operational dashboards and technical debt.
What was A Smattering of Selenium #84?
It was one installment in the Selenium blog’s “Smattering” series: a collection of links on browser automation and related software-development topics, with brief comments from Goucher. The official archive lists #84 among the numbered posts in that series (original post; Smattering tag archive).
Goucher opened by joking that it had been only three months since the previous installment. That remark is about the series’ publishing interval, not a Selenium release schedule or a measured statistic.
What topics did the roundup cover?
Page events and page objects
One linked article discussed DOM Ready and the ordering of page events; Goucher cautioned readers that the comments deserved a “buyer beware” approach. Other links concerned a page object for BrowserID and writing page objects. Goucher noted that the latter reflected how he built page objects, except that he sometimes used Cucumber as a functional runner.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
Test execution and technical debt
A Robot Framework link addressed splitting tests into batches for parallel execution when existing batches stopped being balanced. Another, “The Long Tail of Technical Debt,” examined test-run information and what to do with a particular outcome pattern. The roundup points readers to those discussions; it does not establish that any particular technique is right for every test suite.
Dashboards and other software topics
The links also included “Enterprise Operational Intelligence,” an Etsy story titled “Lessons from Etsy: Avoiding Kitchen Nightmares,” and Bugwatch, which Goucher called “magic,” while observing that magic can sometimes be fun. A link about Rachmaninov’s Third Piano Concerto, played by Selenium, earned his description “just cool.”
Rank #2
Is Selenium 84 a Selenium release?
No. The number 84 identifies the installment in the “Smattering” blog series, as the official tag archive confirms. The post is dated June 11, 2012, and should be read as historical community coverage—not as news about a Selenium version, current browser compatibility, or the present availability of the linked projects.
What does the post say about automation and quality?
It closes with a line attributed to Ben Simo (@qualityfrog / @QualityFrog): “When test automation is made a goal rather than a tool, quality suffers.” The post offers no statistical study or organizational data alongside that statement. Its point is best read as a caution against treating automation itself as the outcome, rather than using it in service of software quality.
Try website screenshots with ScreenshotNeo
For a separate task—capturing a website as an image or PDF—ScreenshotNeo provides a screenshot API and MCP server for developers. It is not a Selenium release or a subject of Goucher’s 2012 roundup; it is an alternative to consider when you need screenshot capture rather than browser-test automation.
ScreenshotNeo accepts a URL in one GET request and can return PNG, JPEG, WebP, or PDF. Its documented options include full-page capture, element capture by CSS selector, device presets, custom CSS and JavaScript, and PDF page settings. See the ScreenshotNeo API documentation for request parameters.
Its clean-shot workflow can accept cookie or consent banners and remove more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each of those steps can be turned off. Bot checks or CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed as clean shots, and response headers report the page verdict and billing status. ScreenshotNeo also offers an MCP server with take_screenshot, get_page_info, and capture_pdf tools for AI agents and MCP clients.
For example, this cURL request saves a WebP screenshot of Stripe:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpReplace YOUR_API_KEY with your API key and change the target URL as needed. The free plan includes 1,000 shots per month without a card; paid plans start at $5 for 3,000 shots. Sign up for ScreenshotNeo’s free plan.
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.
