Free tools Windows power users keep installed
One-click scans. No signup required.
A Smattering of Selenium #82 was a link roundup by Adam Goucher, published on March 13, 2012. It captured a moment in the Selenium community when browser automation was being discussed alongside test design, continuous integration, release risk, and broader QA practice—not just as a way to drive a browser.
What was in A Smattering of Selenium #82?
Goucher’s post was a collection of links and brief commentary, not a Selenium release announcement, product review, or single tutorial. Its opening line—“Someone explain to me why I’m in Toronto and not Florida?”—was a personal quip, rather than a technical claim.
As an Amazon Associate I earn from qualifying purchases.
The roundup ranged well beyond Selenium itself. It pointed readers to PyCon session videos and browser release histories, then connected browser automation to practical testing and software-development concerns:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →- WebDriver and browser interaction: material on using Selenium WebDriver with C#, including Internet Explorer security settings.
- Test structure: discussions of sharing WebDriver instances across test fixtures, browser-specific fixtures, page objects, and PageFactory.
- Testing across tools and languages: links touching Capybara integrations, PHP microtesting, and collecting browser JavaScript errors.
- Continuous integration and development environments: items on Travis CI for Firefox add-ons, RVM and Pik, Autoenv, and Capistrano.
- Quality and release practice: QA experience reports, “Four Principles of Low-Risk Software Releases,” Microsoft browser performance testing, and hiring change agents.
- Page-object examples: the Ruby page-object 0.6.2 release and examples of page objects.
What does this roundup show about Selenium discussions in 2012?
The edition presents browser automation as one part of a larger engineering practice. Its linked subjects bring together the mechanics of controlling browsers, the organization of tests and fixtures, CI, QA experience, and the risks of shipping software. That breadth is the most useful historical takeaway: Selenium-related conversation was not limited to writing scripts that clicked through pages.
#1 Best Overall
Goucher also says he preferred experience reports to repetitive introductory how-to posts, and describes automation as a way to produce information that can start conversations. Those are the author’s editorial views in this post, not measured findings about the field.
How should readers use this as a historical source?
Read the roundup as a snapshot of what its author chose to collect on March 13, 2012. The post documents those topics and references at that time; it does not establish whether the linked tools, versions, integrations, or advice are maintained or applicable today. Check a project’s current documentation and status before relying on any item for present-day work.
The edition supplies no named statistics about Selenium or software testing. A release number or version mentioned in an item is not evidence of a broader trend, adoption rate, or technical result.
Capturing a web page today
ScreenshotNeo is a current website screenshot API and MCP server from Yorker Media, useful when the task is to capture a page as an image or PDF rather than automate an interactive test. It is a different kind of tool from Selenium, not a replacement for WebDriver test coverage. See ScreenshotNeo for details.
Its stated features include accepting cookie-consent banners and removing more than 60 known consent platforms, newsletter popups, and chat widgets before capture, with each step configurable. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and responses identify the page verdict and billing status. Its MCP server exposes screenshot and PDF tools to AI agents and MCP clients.
ScreenshotNeo offers 1,000 shots per month on its free plan without a card; paid plans start at $5 for 3,000 shots. All features are available on every plan. If you want a screenshot API or MCP-based capture workflow, sign up for 1,000 free screenshots a month with no card.
Quick Recap
Rank #4
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.
