ScreenshotNeo
Sign in Get a free key

BlogEngineering

Selenium News and Updates: A Smattering of Selenium 97

A look back at Adam Goucher’s June 29, 2012 Selenium roundup, from HAR capture and WebDriver to pytest, Python requests, and browser channels.

By the ScreenshotNeo team4 October 20263 min read

A Smattering of Selenium #97 was Adam Goucher’s community link roundup, published Friday, June 29, 2012. It covered automated cross-browser JavaScript testing, HAR capture, Firefox authentication, HTTP service stubbing, pytest, Python REST requests, .NET WebDriver packaging, Git rebasing, Python generators, and a Chrome channel update. It is a historical roundup, not a current Selenium release announcement or a complete tutorial for any one tool.

Read the original post on the Selenium blog. The linked items and tools date from 2012; check their current documentation before relying on them in a modern setup.

What the roundup covered

The post gathered links across browser testing and general development rather than focusing on one Selenium feature. Its subjects included:

  • Automated cross-browser JavaScript testing, with particular attention to Internet Explorer.
  • Capturing HTTP Archive (HAR) data through a proxy or Firefox’s NetExport profile extension.
  • Using AutoAuth with Selenium WebDriver for automatic Firefox authentication.
  • RoboHydra, an open-source tool for testing HTTP clients and stubbing services.
  • Parameterized pytest resources and Python’s requests library for RESTful API communication.
  • The state of NuGet packaging for the .NET WebDriver bindings.
  • Git rebasing, Python generators, and an update on Google Chrome’s beta and stable channels.

The roundup supplied links and short descriptions; it did not reproduce the linked tutorials or establish whether their instructions still work today.

How the post discussed HAR capture

One short note compared two approaches available to the author at the time: generating HAR files through a proxy, or using NetExport in a Firefox profile to save data locally or send it to a remote server. Goucher said he preferred the proxy route because it was cross-browser.

That is a 2012 personal preference, not a current compatibility guarantee or a modern comparison of capture tools. The source does not provide enough evidence to recommend a present-day proxy or browser extension.

Why this roundup matters as a historical snapshot

The post shows how Selenium practitioners connected browser automation to the surrounding testing workflow: cross-browser JavaScript checks, authentication, network inspection, service stubs, test parameterization, API clients, and binding distribution. WebDriver was one part of that landscape, not the sole subject.

For readers revisiting a specific technique, use the roundup as a map to the original links and verify current support, package names, browser behavior, and security practices against the maintained documentation for the tool you choose. The 2012 post does not validate any present-day setup.

Capture a page today without setting up a browser

If your reason for reading the HAR discussion is that you need a visual record of a page, a screenshot API is a different tool: it returns an image or PDF of the rendered page rather than a HAR network archive. For current page screenshots, ScreenshotNeo is the first alternative to try: it removes cookie banners, popups, and chat widgets before capture, and bills only clean shots.

For a DIY HAR workflow, use the proxy or browser tooling documented for your current stack; this 2012 roundup does not contain a complete runnable HAR setup. For a screenshot, one GET request is enough. See the ScreenshotNeo API documentation for the available parameters.

Or skip the browser setup

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

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"},
    timeout=90,
)
open("shot.webp", "wb").write(r.content)
const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await Bun.write('shot.webp', res);

ScreenshotNeo removes cookie banners, popups, and chat widgets before the shot. Bot checks, blank pages, and failed loads are never billed. An MCP server lets AI agents take screenshots, and 1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000. This returns a screenshot, not a HAR file.

Sign up for 1,000 free screenshots a month, with no card required.

FAQ

Who wrote A Smattering of Selenium #97?

Adam Goucher wrote the roundup for the Selenium blog.

When was it published?

Friday, June 29, 2012.

Was it a Selenium release announcement?

No. It was a community link roundup spanning Selenium-related testing and broader developer topics.

Does ScreenshotNeo capture HAR files?

No. ScreenshotNeo captures rendered pages as screenshots or PDFs. HAR capture records network activity and requires an appropriate browser or proxy workflow.

Keep reading