ScreenshotNeo
Sign in Get a free key

BlogEngineering

Selenium News and Updates: A Smattering of Selenium 73

Published January 5, 2012, A Smattering of Selenium #73 linked two Ruby gems and two testing-focused article series. Here is what the roundup covered.

By the ScreenshotNeo team4 October 20264 min read

A Smattering of Selenium #73 was a community link roundup, not a Selenium release announcement. Adam Goucher published it on Thursday, January 5, 2012. It pointed readers to two Ruby gems, a three-part Sauce Labs series on building a testing framework, and a three-part continuous-integration cost/value series by Johanna Rothman. The “73” is the roundup’s issue number, not a Selenium product version. Read the original post in the Selenium blog archive.

What was in A Smattering of Selenium #73?

The archived post begins “Two Ruby gems…” and then groups links around test automation and engineering practice. The following descriptions summarize what the 2012 roundup said; they do not establish whether the linked software, articles, or services remain available or maintained today.

Resource What the roundup said it covered
rwebspec-webdriver An executable functional specification for web applications, using RSpec syntax and Selenium-WebDriver.
loadable_component A Ruby implementation of LoadableComponent.
Sauce Labs testing-framework series Three installments: “Testing Concepts,” “Base Classes,” and “Putting it all together.”
Johanna Rothman series Three installments titled “Is the Cost of Continuous Integration Worth the Value on Your Program?”

What the two Ruby gems were for

rwebspec-webdriver

The roundup characterized this gem as a way to express functional specifications for web applications in RSpec syntax and execute them with Selenium-WebDriver. That description places it at the boundary of readable specification and browser-driven behavior checks. The historical post does not document installation, APIs, compatibility, or present-day maintenance, so treat the description as a pointer for archive research rather than current setup guidance.

loadable_component

This was described as a Ruby implementation of LoadableComponent, a pattern for representing a page or component whose readiness can be checked before a test acts on it. The source establishes only that the roundup linked a Ruby implementation; it does not give enough detail to reproduce its interface or recommend it for a current project.

The two article series

Sauce Labs: building a testing framework

The roundup linked a three-part sequence covering “Testing Concepts,” “Base Classes,” and “Putting it all together.” Taken together, those titles suggest a progression from concepts, to shared test structure, to assembly of a framework. That is a reading guide based on the sequence titles, not a claim about the articles’ exact technical recommendations.

Johanna Rothman: continuous integration cost and value

The three linked installments asked whether the cost of continuous integration is worth the value on a program. Their presence broadens this issue beyond browser automation into the economics and organizational tradeoffs around CI. The roundup does not supply a numerical cost model or a conclusion that applies universally.

Do not confuse issue 73 with Selenium 2.16

The Selenium archive lists Selenium 2.16 Released: Welcome to 2012! on the same date as Smattering #73, January 5, 2012. They are separate posts: 2.16 is the release announcement; 73 is the number of the general community roundup. The 2012 archive page lists both entries separately.

How to use this roundup today

  1. Use it as a historical index. It records what Selenium community links Adam Goucher chose to surface on that date.
  2. Follow the original links cautiously. The issue dates to 2012. Check a project’s current repository, release history, compatibility notes, and documentation before using it.
  3. Keep the categories distinct. The gems are software leads; the two article series are reading leads. Neither establishes current support or endorsement.
  4. Look for current guidance for current projects. This roundup is not a Selenium setup guide and does not explain modern browser, driver, or language configuration.

Capturing a page from a test run

If your reason for reading an old Selenium roundup is to keep visual evidence of a page, a screenshot can complement functional checks. For a screenshot of a publicly reachable page, ScreenshotNeo provides a website screenshot API and MCP server. It is a separate capture option; it does not run Selenium tests or validate their assertions.

Or skip the browser setup

Send a GET request with the target URL. This example saves a WebP response as shot.webp; replace the URL and API key with your own values. See the ScreenshotNeo API documentation for request options.

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 accepts cookie or consent banners like a visitor and removes more than 60 known consent platforms, newsletter popups, and chat widgets before capture; each cleanup step can be turned off. Bot checks, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. Its MCP server exposes take_screenshot, get_page_info, and capture_pdf for AI agents and MCP clients. The free plan includes 1,000 shots per month with no card; paid plans start at $5 for 3,000 shots. ScreenshotNeo is a product of Yorker Media. Sign up for 1,000 free screenshots a month, with no card.

FAQ

When was Selenium Smattering 73 published?

Thursday, January 5, 2012, according to the Selenium archive.

What Ruby gems did Selenium #73 mention?

rwebspec-webdriver and loadable_component.

Was Selenium 2.16 the same thing as Smattering #73?

No. The archive lists a Selenium 2.16 release announcement and the #73 general roundup as separate posts published on the same date.

Does the roundup confirm that its linked gems still work?

No. It records their descriptions in 2012 and does not establish current availability, compatibility, or maintenance.

Keep reading