ScreenshotNeo
Sign in Get a free key

BlogEngineering

Selenium News and Updates: A Smattering of Selenium 67

A guide to Selenium’s October 2011 roundup #67: its topics, historical context, and what the links do—and do not—tell developers today.

By the ScreenshotNeo team4 October 20265 min read

“A Smattering of Selenium #67” is a historical Selenium community link roundup published on October 27, 2011—not a current release announcement. Adam Goucher’s post points readers to articles and projects about behavior-driven development, continuous integration, AJAX page loading, SVG game testing, Selenium RC speed, and queries after load tests. Its links are useful as a snapshot of the testing topics circulating in 2011; they do not establish what works with Selenium today.

1. What was “A Smattering of Selenium #67”?

It was one entry in Selenium’s series of community link roundups. The official archive lists the post under 2011, in the General category and tagged “Smattering.” Adam Goucher published it on Thursday, October 27, 2011. Read the original post and check the Selenium blog archive.

The post is best read as an annotated set of pointers. It is not a release note, a formal comparison, or a benchmark report. Goucher raises a question about whether the Spinach BDD framework had Selenium support, but his expectation that it might is speculation, not confirmation of compatibility.

2. Topics covered in the roundup

Topic What the roundup points to How to interpret it
Behavior-driven development Spinach, described by Goucher as a Cucumber-esque BDD framework advertised as having “less regex magic.” The post wonders whether Spinach had gained Selenium support. That question is not evidence that support existed, and it says nothing about the framework’s present state.
Large CI systems An article about coping with large continuous integration systems. A pointer to CI practices and scale concerns, not a specific Selenium configuration or current deployment recommendation.
AJAX testing An article about “reintroduced page loading” for AJAX testing in Selenium. A historical discussion of page-load behavior and asynchronous applications.
SVG and games Testing an SVG game, plus Jason Huggins’ Selenium robot playing Angry Birds. Examples of browser automation applied to graphical and interactive experiences.
Selenium RC speed An article about faster Selenium test execution, specifically concerning Selenium RC. The scope is Selenium RC in 2011; do not generalize it to current Selenium components or browsers.
After-load-test queries BrowserMob ad hoc queries to use after Selenium-based load runs. A pointer to analyzing load-test results, not a claim that Selenium itself is a load-testing system.

The post also asks whether XPath engine speed differs. It offers no test data or comparison, so the aside should be treated as an unanswered question, not performance evidence.

3. What developers can take from it today

  1. Keep the date attached. The roundup describes tools, concerns, and terminology from 2011. Label it as historical when citing it.
  2. Follow original links for historical context. The roundup is a map to the topics it mentions; it does not independently validate every linked article or project.
  3. Verify current compatibility separately. Check current project documentation and release information before choosing a framework, browser integration, or test strategy. The post’s Spinach speculation is not a present-day compatibility check.
  4. Separate test automation from load analysis. The BrowserMob reference concerns queries after Selenium-based load runs. It does not establish that browser automation alone measures load behavior adequately.

The useful takeaway is the range of concerns: test organization, CI scale, asynchronous page behavior, nonstandard browser content, execution time, and analysis after load runs. The roundup is evidence that these concerns were being discussed in the Selenium community at the time, not a set of instructions to apply unchanged.

4. What the roundup does not establish

  • It does not announce a Selenium release or define current Selenium behavior.
  • It does not confirm that Spinach supported Selenium, then or now.
  • It does not compare XPath engines or publish timing measurements.
  • It does not provide a current recommendation for CI, browser grids, or hosted testing services.
  • It does not include a statistic, formal product comparison, or firsthand evaluation of the linked services.

The Selenium site’s current Development Partners listing is separate ecosystem context. It should not be read as evidence that those companies appeared in this 2011 roundup or that an affiliate relationship exists. See Selenium’s official site.

5. Capture a page from a Selenium workflow

If you are preserving a test result or documenting a page state, a screenshot can complement DOM assertions and logs. A local browser setup gives you control over browser startup and capture timing. For example, this minimal Python script uses Selenium WebDriver and saves a screenshot after navigation. Install Selenium and the browser driver appropriate for your environment before running it.

from selenium import webdriver
from selenium.webdriver.chrome.options import Options

options = Options()
options.add_argument("--headless=new")
options.add_argument("--window-size=1440,1000")

driver = webdriver.Chrome(options=options)
try:
    driver.get("https://example.com")
    driver.save_screenshot("page.png")
finally:
    driver.quit()

This captures the current viewport. For asynchronous pages, wait for a meaningful condition before saving; a fixed delay can be flaky and slow. Use an explicit wait tied to an element or state your test needs. A screenshot is useful evidence, but it does not replace assertions about application behavior.

6. Or skip the browser setup

ScreenshotNeo is a website screenshot API and MCP server. One GET request can return an image or PDF, and its option set includes viewport and device presets, full-page capture, element capture, selector waits, custom CSS and JavaScript, cookies, headers, and more. See the ScreenshotNeo API documentation.

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

Python:

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)

Node.js:

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);

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 step can be turned off. Bot checks, CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing, and response headers report the page verdict and billing status. 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 a month with no card; paid plans start at $5 for 3,000 screenshots.

Create a free ScreenshotNeo account to get 1,000 screenshots a month with no card.

7. FAQ

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

No. It was a community link roundup published on October 27, 2011.

Did the post confirm Selenium support in Spinach?

No. Goucher wondered whether support had arrived and expressed an expectation; the post does not verify it.

Does the roundup prove one XPath engine was faster?

No. It raises the topic as a question and supplies no measurements.

Is its Selenium RC speed discussion applicable to current Selenium?

Not by itself. The linked subject is specifically Selenium RC, and the post is historical. Check current documentation for present-day behavior.

Keep reading