A Smattering of Selenium #82 is a historical link roundup by Adam Goucher, published March 13, 2012—not a Selenium release note, tutorial, or current product comparison. It captures the browser-automation and software-testing conversations Goucher was collecting at that moment.
What was in A Smattering of Selenium #82?
The edition brings together links and brief commentary across Selenium WebDriver, browser testing, quality assurance, continuous integration, and broader development practice. Its opening line is a personal quip: “Someone explain to me why I’m in Toronto and not Florida?”
Goucher also says he prefers experience reports to repetitive introductory how-to posts, and presents automation as a way to produce information that can start conversations. Those are his editorial views, not measured findings about testing.
Topics the roundup connected
WebDriver and browser-specific testing
Several items concern interacting with web pages through Selenium WebDriver for C#, including security settings for Internet Explorer. The roundup also points to discussions of sharing WebDriver instances across test fixtures and organizing fixtures around particular browsers.
Windows 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 reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match#1 Best Overall
Page objects and testing practice
The links include the Ruby page-object 0.6.2 release and page-object examples, as well as material about PageFactory, Capybara integrations, PHP microtesting, and collecting browser JavaScript errors. Taken together, these topics show how the roundup ranged from test design patterns to practical ways of observing browser behavior.
CI, releases, and the wider development workflow
Other subjects include Travis CI for Firefox add-ons, RVM and Pik, Capistrano, autoenv for directory-level scripts, Microsoft browser performance testing, and “Four Principles of Low-Risk Software Releases.” The edition also points readers to PyCon session videos and browser release histories that Goucher described as historically interesting.
QA and team experience
Quality-assurance experience reports and a piece about hiring change agents broaden the collection beyond test scripts. The roundup treats automation as part of a larger conversation about how teams learn from software and organize their work.
How to read this roundup now
Use the post as a dated snapshot of what one Selenium community contributor found worth sharing in March 2012. It does not establish that the linked projects, versions, services, or advice are still maintained or available today. Check the original source and the current project documentation before relying on any individual link or technical recommendation.
The edition supplies no named statistics about Selenium or software testing, and it should not be treated as independent evidence for a technical claim. Its value is in the breadth of topics it connects: browser automation, maintainable test structures, CI, release risk, and QA practice.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Capture a browser test result without running a local browser
If your current work involves documenting a web page or capturing a test result, you can still run Selenium locally; this 2012 roundup is not a current how-to for configuring Selenium. For a screenshot without browser setup, ScreenshotNeo offers a website screenshot API and MCP server for developers. A single GET request can return an image or PDF, and its cleanup options can accept cookie banners and remove known consent banners, newsletter popups, and chat widgets before capture. See ScreenshotNeo for the service overview.
Or skip the browser setup:
Use this cURL call to capture a page as WebP; replace the example URL with the page you need and supply your API key. Full request options are in the ScreenshotNeo API documentation.
Quick Recap
Rank #4
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpCookie banners, popups, and chat widgets are removed before the shot. Bot checks, blank pages, and failed loads are never billed; an MCP server lets AI agents take screenshots. The Free plan includes 1,000 screenshots a month with no card, and paid plans start at $5 for 3,000. Sign up free for 1,000 screenshots a month, with no card required.
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.
