“A Smattering of Selenium #72” was a historical Selenium link roundup, not a current release announcement. Written by Adam Goucher and published on January 3, 2012, it collected ten links on browser automation and software testing, including WebDriver waits, Android WebDriver, dynamic pages, and continuous integration. Goucher noted that some links were already “a month old (or older!).”
What the January 2012 roundup covered
The post brought together short notes and links spanning several testing concerns. Its subjects show the breadth of Selenium-related discussion at the time; they do not establish that the linked tools or advice remain maintained, compatible, or suitable today.
| Topic | What the post linked to |
|---|---|
| Localization | An article about using Zend_Translate in PHP applications. |
| Behavior-driven testing | A post about using Spinach with Selenium. Goucher described Spinach as a different implementation of Cucumber, while noting that this characterization might oversimplify it. |
| Mobile browser automation | An announcement introducing Android WebDriver. |
| Synchronization | A WebDriver article comparing explicit and implicit waits for an element to load. |
| GWT testing | An article on testing GWT applications with Selenium and WebDriver; Goucher drew attention to its third problem. |
| Browser choice | A guide to browser adoption rates, offered as context for browser automation. |
| Monitoring | A link about integrating Selenium test cases into Nagios. |
| Continuous integration | A post about CI principles and task sizing. |
| Dynamic pages | A link about locating AJAX elements with Selenium 2 and WebDriver, which Goucher compared with WebDriverWait. |
| Ruby automation APIs | A return to an earlier link about three Ruby automated-testing APIs. |
How to read it today
The roundup is useful as a snapshot of what Selenium practitioners were discussing in early 2012: synchronization, browser and mobile automation, dynamic content, and fitting tests into monitoring and CI workflows. It is not evidence of current Selenium news or a guide to present-day setup.
- The post itself gives no browser-adoption figures; it only links to a separate article on that subject.
- It does not verify whether any linked project or recommendation is still maintained or compatible with current software.
- It names no contemporary cloud-testing provider and makes no purchase recommendation.
For current decisions, check the present documentation and maintenance status of the specific Selenium components or related projects you plan to use rather than relying on a link roundup published in 2012.
#1 Best Overall
Screenshot API alternative for capturing test pages
If your goal is to save a page image or PDF from an automated workflow, ScreenshotNeo is a website screenshot API and MCP server from Yorker Media. It is an alternative to explore first for clean captures: it removes known consent banners, newsletter popups, and chat widgets before capture, and only clean shots are billed. Its website screenshot API can return PNG, JPEG, WebP, or PDF.
One-request example
For example, use cURL to capture a URL:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo documentation for request options. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits are not billed; response headers indicate the page verdict and billing status. Its MCP server provides take_screenshot, get_page_info, and capture_pdf tools for AI agents and MCP clients.
The Free plan includes 1,000 shots per month without a card. Paid plans start at $5 for 3,000 shots; every feature is available on every plan. Sign up for ScreenshotNeo and get 1,000 free screenshots a month with no card.
Quick Recap
Rank #2
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.
