ScreenshotNeo
Sign in Get a free key

BlogEngineering

Selenium News and Updates: A Smattering of Selenium 82

A look back at Adam Goucher’s March 13, 2012 Selenium roundup, from WebDriver and page objects to CI, QA, and safer software releases.

By the ScreenshotNeo team4 October 20263 min read

“A Smattering of Selenium #82” was a link roundup by Adam Goucher, published Tuesday, March 13, 2012. It collected articles, releases, and commentary about Selenium WebDriver and the wider work of testing and software development. It is a historical snapshot, not a current Selenium release announcement, tutorial, or tool comparison.

The edition is useful for seeing how browser automation was discussed alongside maintainable test design, continuous integration, release risk, and QA practice. Its links show what Goucher chose to highlight at that moment; they do not establish whether the linked projects, versions, or advice are still current.

What was in “A Smattering of Selenium #82”?

The roundup ranged well beyond Selenium itself. Its topics included:

  • Conference learning: videos of PyCon sessions for people who missed the conference.
  • Browser history and performance: browser release histories and Microsoft browser performance testing.
  • WebDriver: interacting with web pages using Selenium WebDriver for C#, including Internet Explorer security settings.
  • Page objects: the Ruby page-object 0.6.2 release and examples of page-object use, alongside discussion of PageFactory.
  • Test setup and reuse: sharing WebDriver instances across test fixtures and using browser-specific fixtures.
  • Continuous integration and browser tooling: Travis CI for Firefox add-ons, Capybara integrations, and browser JavaScript error collection.
  • QA and engineering practice: experience reports, PHP microtesting, RVM and Pik, Capistrano, hiring change agents, and “Four Principles of Low-Risk Software Releases.”
  • Developer workflow: Autoenv, described as a tool for directory-level scripts.

This was a curated set of pointers, not a unified argument or a claim that every linked technique was broadly adopted. Goucher also said he preferred experience reports to repetitive introductory how-to posts, and presented automation as a way to produce information that can start conversations. That is the author’s editorial perspective, not a measured finding.

Why the roundup matters as a historical snapshot

The edition places browser automation in a broader engineering context. A test suite depends on more than commands that drive a browser: teams also have to decide how tests share setup, how page interactions are represented, how failures are observed, and how changes move through CI and release processes. The roundup’s range of links makes those connections visible.

It also captures a particular moment in the browser ecosystem. References to Internet Explorer settings, browser release histories, and specific tool versions belong to that period. They should be read as historical details, not as current setup instructions or recommendations.

How to read the linked resources today

  1. Start with the original context. Treat the items as links Goucher collected in March 2012. The roundup does not independently validate their claims.
  2. Check dates and versions. Any version number or browser-specific instruction may have been superseded.
  3. Verify project status before relying on a link. The edition alone does not establish whether a project is maintained, available, or compatible with current browsers.
  4. Separate historical interest from present-day guidance. The roundup can show what practitioners were discussing without proving that a particular approach is right for a modern test stack.

ScreenshotNeo for capturing pages in browser workflows

For a current way to capture a page involved in a browser testing workflow, ScreenshotNeo is a website screenshot API and MCP server for developers. It can return a PNG, JPEG, WebP, or PDF from one GET request. Its capture options include full-page screenshots, CSS selector element capture, device and viewport settings, custom headers and cookies, and waiting for a selector, delay, or network idle. See the ScreenshotNeo API documentation for parameter details.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webp

ScreenshotNeo accepts cookie and consent banners like a visitor before capture and removes more than 60 known consent platforms, newsletter popups, and chat widgets; each of those steps can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers identify the page verdict and whether the request was billed. Its MCP server provides take_screenshot, get_page_info, and capture_pdf for Claude, Cursor, and other MCP clients.

The Free plan includes 1,000 screenshots per month with no card. Paid plans start at $5 for 3,000 screenshots; yearly billing gives two months free, and every feature is on every plan. Sign up for 1,000 free screenshots a month, with no card required.

FAQ

Was “A Smattering of Selenium #82” a Selenium release announcement?

No. It was a roundup of external links and commentary, not a Selenium release note.

Who wrote it, and when was it published?

Adam Goucher published it on Tuesday, March 13, 2012.

Does the roundup tell developers which linked tools are still supported?

No. It records the edition’s historical links and discussion; current status must be checked independently.

Keep reading