“A Smattering of Selenium #64” is a historical roundup, not current Selenium news: Adam Goucher published it on the official Selenium blog on October 17, 2011. Its brief links and comments capture the testing and development concerns of that moment, from Selenium IDE and WebDriver to collaboration, test infrastructure, and parallel testing.
What the October 2011 post is
Goucher’s post is a curated set of links with short reactions, rather than a Selenium release announcement or a single technical tutorial. He opens with the aside, “How did I fall behind again already?!?!”, before moving through presentations, engineering practices, and testing-related articles. The original Selenium Project post is the best source for its exact links and context.
As an Amazon Associate I earn from qualifying purchases.
The themes behind the links
Demonstrating work and learning by doing
The roundup points to “Automation Isn’t All Shiny Toys” and advice to share videos of time-based work goals, illustrated by Dave’s Q3/2011 review. Goucher notes that the final two screencasts in that example relate directly to Selenium. Another link, Aslak Hellesøy’s “The training wheels came off,” drew Goucher’s praise in connection with Selenium IDE. Taken together, these links show an interest in making engineering work visible and learning tools through practice; they are not a current assessment of the linked material or software.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Making automation part of team work
Feature switching appears as a way for teams to collaborate while doing automation. The idea is organizational as much as technical: teams can coordinate changes and automation work without treating testing as an isolated final stage. The post offers this as a link and topic, not a detailed implementation guide.
#1 Best Overall
Building a dependable test environment
Several links concern the infrastructure around tests: hosting a repository for build artifacts, automated configuration management using Puppet and Geppetto, and learning tools by “diving down the stack.” These concerns remain recognizable in software delivery, but the roundup does not establish whether any named project or service is maintained or suitable today.
Looking at Selenium internals and scaling
The post links David Beazley’s slides about Python’s Global Interpreter Lock (GIL), a report on logging Selenium 2 events in Twist as a product-centric spike, and “The 5 steps to the parallel web testing epiphany.” The Twist item speculates about possible relevance to extending WebDriver. These are snapshots of technical discussion in 2011, not documentation of current WebDriver behavior or a present-day parallel-testing recipe.
How to read it today
The post is useful as a small historical record of what Selenium practitioners were discussing in 2011: demonstrating progress, collaborating around automation, managing artifacts and configuration, understanding underlying tools, and scaling browser tests. The Selenium Smattering archive places #64 among other posts from that period, but archive context does not verify the present-day status of projects linked from an old roundup.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Use the post to understand the period’s conversations, not as a current news feed.
- Check current official documentation before adopting a browser-testing tool, framework, or service mentioned in it.
- Do not infer current Selenium releases, project support, or vendor partnerships from this 2011 post.
Capturing current web pages for test work
If you need screenshots of pages as they behave now, treat that as a separate task from reading the historical roundup. A browser-driven workflow can capture a page, but requires you to manage the browser setup and page state yourself. For an API-based alternative, ScreenshotNeo returns a screenshot or PDF from one GET request; it removes known consent banners, newsletter popups, and chat widgets before capture, and only clean shots are billed.
Or skip the browser setup
For a PNG, JPEG, or WebP screenshot, replace the target URL and API key in this cURL request. See the ScreenshotNeo API documentation for request options.
Quick Recap
Rank #4
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpScreenshotNeo accepts known cookie and consent banners, removes more than 60 known consent platforms plus newsletter popups and chat widgets before capture, and lets you turn each cleanup step off. Bot checks and CAPTCHAs, blank pages, timeouts, failed loads, and cache hits cost nothing; response headers report the page verdict and billing status. Its MCP server offers take_screenshot, get_page_info, and capture_pdf for AI agents and other MCP clients. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000 shots. Sign up for ScreenshotNeo’s free plan.
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.
